Automatic update from web-platform-tests
Change self to 'self' in CSP frame-ancestor test (#45640)
--
wpt-commits: 10bcb6d35b5a9e9edf958f9ef1e14897f3710709
wpt-pr: 45640
Automatic update from web-platform-tests
[line-clamp] Make `line-clamp` create a new BFC
Although `-webkit-line-clamp` has always created an independent
formatting context, our prototype implementation of `line-clamp`
initially made it so the `line-clamp` property (but not
`-webkit-line-clamp`) didn't necessarily create one.
However, in the course of implementing this proposal, the fact that it
did not necessarily create a new BFC raised issues, such as how nested
line-clamps should work, or how floats inside a line-clamp container
should affect floats outside it. These problems go away by having
line-clamp create a new BFC, and this CL takes that route.
This patch also removes
`BlockLineClampData::is_original_line_clamp_context`, which was needed
to be able to distinguish whether `(-webkit-)line-clamp` was specified
on the current block element, or whether it inherited its line clamp
data from its parent. With this change, checking if the current block
is a new BFC is enough.
Bug: 40336192
Change-Id: I8a16ec18ce1653caaf1c7d06280a2a7e4604a946
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5453431
Commit-Queue: Andreu Botella <abotella@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1287280}
--
wpt-commits: 85681c669ff292c3c55bd088bf13fd0cc038d7bd
wpt-pr: 45709
Automatic update from web-platform-tests
Add test for external script hashes in content-security-policy/script-src/script-src-strict_dynamic_hashes (#44769)
* Add test for external script hashes in strict-dynamic
* Use sync test
--
wpt-commits: 947b3ebca48d50d9efffc4e196e61d146e983d86
wpt-pr: 44769
Automatic update from web-platform-tests
[anchor] Implement CSSPositionTryDescriptors
CSSPositionTryDescriptors is a CSSStyleDeclaration which restricts
which properties are valid, which is a new concept in Blink.
This CL implements this by:
- Adding a new parsing mode which is stored on the CSSPropertyValueSet
within the rule. This ensures that we can't smuggle in invalid
properties using cssText.
- Filtering properties during setProperty. This ensures that e.g.
setProperty('color', ...) doesn't work.
Somehow, CSSPositionTryDescriptor is not inheriting the anonymous
named getter/setter from the parent, which is actually what we want
here. (If this is a bug or something and is changed later, the WPT will
fail).
The indexed property getter also doesn't seem to work. This is not
covered by the tests currently. The problem is tracked by
Issue 333965945.
Change-Id: I5fa1b600ed50633a9eb9aa8cfeb43726d64ecf90
Bug: 333967631, 333965945
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5447110
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1287213}
--
wpt-commits: 9fcc5e1b74b4eec90b2dd05c8f06fb2346651f43
wpt-pr: 45683
Automatic update from web-platform-tests
Await web font loading in css-scoping tests
Some tests did not pass because the web font did not finish loading
before the rendered widths were checked. Await document.fonts.ready to
make the tests predictable.
Bug: 333457515
Change-Id: I830cc11b4ba7a4c8a5579777712085cb3f7e5a1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5447137
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Munira Tursunova <moonira@google.com>
Cr-Commit-Position: refs/heads/main@{#1287178}
--
wpt-commits: 6eb4b61b016f28234bd31d90d8e4e7ca2037375a
wpt-pr: 45684
Automatic update from web-platform-tests
Deflake compression-dictionary WPT
WPT tests for compression-dictionary are flaky on some bots. There are
two reasons:
1. Installing a dictionary is slow. This requires disk cache access
and SQLite DB access.
2. Handling Clear-Cache is slow. All tests of Compression dictionary
are clearing caches using Clear-Cache HTTP header after running
tests.
To resolve the flakiness, this CL increases the timeout for checking
available dictionaries, and sets a longer timeout for all tests.
Also this CL splits the tests of Clear-Cache into three files.
Bug: 333916144
Change-Id: I9e41083db599ae2f06f51bfe1abac4aba0a6d472
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5445912
Reviewed-by: Patrick Meenan <pmeenan@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1287111}
--
wpt-commits: 73b5c2474612889749dfa8f8db0645c07694e9fb
wpt-pr: 45674
Automatic update from web-platform-tests
compute pressure: Add web test for multiple calls to PressureObserver.observe()
The buggy behavior described in issue 333957909 has been fixed by
https://crrev.com/c/5384658 but we want to make sure this does not
happen again.
Bug: 333957909
Change-Id: Ia1ac67b534eeca3bb3cc1c7832e8df07d3e7847e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5447142
Auto-Submit: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286881}
--
wpt-commits: dce39b08c51964db0677e1ce1c5c03b658952297
wpt-pr: 45689
Automatic update from web-platform-tests
Add WPT tests validating layers with transforms
If the canvas has a global shadow, the transform must not be applied on
the shadow filter. This currently doesn't work in Blink for layers: the
transform affects the shadow of the layer.
Bug: 40257559
Change-Id: Ib765073660b1c2b70cf8934603ab124cef4fdca9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5434678
Reviewed-by: Yi Xu <yiyix@chromium.org>
Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286817}
--
wpt-commits: 44a19cee8dc1860c4bfff0070f4061b27976a7c3
wpt-pr: 45691
Automatic update from web-platform-tests
[anchor-pos] Adjust the scroll offsets by the inset area offsets.
Previously the scroll offsets were set up ignoring inset-area, (and
other insets potentially - but that is for a followup).
Adjust the scroll offset by the inset-area if present.
Bug: 333614330
Change-Id: I37e9910f38c81a22b97deba1ac0a171fc5432090
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5448340
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286853}
--
wpt-commits: 60e96d833f5ca63f4ba0da8f3bf07e835b94aec2
wpt-pr: 45693
Automatic update from web-platform-tests
Introduce PointerEvent.deviceProperties
This change replaces deviceId on the PointerEvent interface with a new interface, deviceProperties. DeviceProperties contains one member, uniqueId, which functionally behaves the same as the outgoing deviceId.
Spec: https://github.com/w3c/pointerevents/pull/495
Bug: 330760871
Change-Id: I0f1a9f7d5589f790d94f498a38bfdf55b6f51073
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5388651
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Sahir Vellani <sahir.vellani@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1286827}
--
wpt-commits: 4013b5285c0977d16542695ae2ed47184730f331
wpt-pr: 45420
Automatic update from web-platform-tests
Short-circuit interpolation calculation for a static-valued property
With the exception of cross-fade interpolations, we can sample a single
keyframe and use its value throughout the animation if the property
is constant-valued. For an animation of the background property that
only explicitly sets the background color, we can short-circuit the
work when applying the animation effect for all of the implicitly set
properties.
Bug: 333861763
Change-Id: Id5634a2656b5e739a91d9593a3ff7c5bb58a85b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5426601
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286714}
--
wpt-commits: 066959a2f2e30a073beea8b71d3bde62c9d058e3
wpt-pr: 45612
Automatic update from web-platform-tests
[css-scroll-snap] Adopt focused, targeted, block priority order
As agreed to in a recent spec issue[1], when re-snapping after a
layout change, if it is not possible to follow the selected targets in
both axes, we should select an axis to follow. Priority should be
given among axes according to:
1. the axis with a focused area, if any,
2. the axis with a targeted [2] area, if any,
3. the block axis.
[1]https://github.com/w3c/csswg-drafts/issues/9622#issue-2006578282
[2]https://drafts.csswg.org/selectors/#the-target-pseudo
Bug: 329250094
Change-Id: Idef6ddbbe0f613ec32f220c89848ea809fd10922
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5444525
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286690}
--
wpt-commits: 8905c6f20edb8e2e2ecd34e6a5f850bbbe6691ae
wpt-pr: 45651
Automatic update from web-platform-tests
Fix popover-focus-2.html WPT
We started failing this WPT after this PR was merged:
https://github.com/web-platform-tests/wpt/pull/43146
The assert we are failing is about which element is focused after
disabling a button, and we are not focusing that disabled button, so I
tweaked the assertion to say that we should not be focusing the button.
I'd be worried that we are diverging from firefox behavior here, but
based on wpt.fyi firefox is already failing the test anyway.
Bug: 325981758
Change-Id: I66d2d86e11546ce4ca11db001b85e5f36d5bccde
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5403252
Auto-Submit: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286654}
--
wpt-commits: b0c732841856e0a1d357048f601805140e1596f2
wpt-pr: 45391
Automatic update from web-platform-tests
IndexedDB: fix structured-clone.any.js WPT
This entire test suite was broken by
a1a458bfd3
To restore IDB test coverage, the new (tentative and unimplemented,
AFAICT), type is only tested if it exists.
The other IDB test that started failing with this change,
idb-binary-key-roundtrip.htm, is unchanged because in that case only
one new test is failing rather than the entire suite, i.e. overall
test coverage is not affected.
Bug: 333225369
Change-Id: I45732d279274561b3b2117ac7cede78fe408cdb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5448168
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286580}
--
wpt-commits: 50396a2ab670bb5b5a75072645a3d8f7de55e728
wpt-pr: 45670
Automatic update from web-platform-tests
[shared storage] Implement the Shared-Storage-Cross-Origin-Worklet-Allowed response header check
When: When creating a cross-origin worklet, require the
"Shared-Storage-Cross-Origin-Worklet-Allowed: ?1" response header,
or the request should fail (similar to the handling for CORS failure).
How: When creating the request (in
SharedStorageURLLoaderFactoryProxy::CreateLoaderAndStart), set
the destination to kSharedStorageWorklet. In
CorsURLLoader::OnReceiveResponse, for cross-origin request with
destination kSharedStorageWorklet, validate the response header.
Note that shared storage worklet request doesn't allow redirects,
so it's sufficient to check inside `OnReceiveResponse` only.
Spec patch: 9507e05157/spec.bs
NO_IFTTT=Not adding the destination to request.idl, because the shared storage worklet request is not visible to service workers / JS.
Bug: 332564979
Change-Id: I6c2a07473527ede995cf4bd337d293f3168351bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5417333
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Dominic Battre <battre@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286573}
--
wpt-commits: 73d81b016f6e9925a40833c42efc75f7de4bfcae
wpt-pr: 45481
Automatic update from web-platform-tests
Element collapsing thru should collapse with its children
If the top and bottom margins of an element collapse through, then this
patch treats the bottom margin as collapsing with its children, even if
`height` doesn't compute to zero.
Co-authored-by: Martin Robinson <mrobinson@igalia.com>
--
wpt-commits: e2b6a0217ab27012c3f18477dda3f9f8ff000592
wpt-pr: 45671
Automatic update from web-platform-tests
Combine 2d.layer.global-states alpha tests into canvas grid tests
This cuts down the number of 2d.layer.global-states test files by
half. Ideally, we would combine even more variants into a larger grid,
using even fewer files, but since some of the test variant are
currently failing in Blink, keeping them in separate files allow us to
mark some of the variants as failing in the TestExectations file.
Bug: 40257559
Change-Id: Iaec24da6de30793c84f5abf5fc630e505ae37011
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5430857
Reviewed-by: Yi Xu <yiyix@chromium.org>
Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286465}
--
wpt-commits: be54d5ab0bf9bc1de2b7134305b7a8849cfbb037
wpt-pr: 45680
Automatic update from web-platform-tests
[anchor] Mark PositionedMovementLayout for null-AnchorEvaluator styles
Regular style recalcs (that are not interleaved from OOF layout)
evaluate anchor*() functions without an AnchorEvaluator, which means
the fallback behavior is always taken. This means if we initially have
some style with left:10px, and then (in a separate lifecycle) change
the specified value to left:anchor(--a right,10px), the ComputedStyle
diffing will not be able to tell that something changed (because it
didn't: anchor() resolves computed-value time). Yet we still need
to invalidate layout in this situation, otherwise we'll never enter
the interleaving OOF recalc and evaluate the anchor() function
for real.
Therefore, this CL (effectively) marks for PositionedMovementLayout
in this situation. I do not actually set the the flag in the diff,
however, because the decision to invalidate is based on the new
style alone (i.e. no actual diffing).
Fixed: 333858786
Change-Id: I49d08c0551ae2ce54d08b6ec947e56c5514c0a61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5445690
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286396}
--
wpt-commits: 1608f50e923836a9063c64c2f5f177c408a48086
wpt-pr: 45668
Automatic update from web-platform-tests
[PEPC] Limit min/max-height/width for PEPC
Put limits on what the min/max-width/height can be.
The min-height will have to be at least 1em
The max-height will have to be at most 3em
Widths are enforced by building an expression that makes use of
calc-size:
The min-width will have to be at least fit-content.
The max-width will have to be at most 3x fit-content.
Bug: 1462930
Change-Id: Idb00f9614cde69e4ff2ca295ca5e89b85b3d0f04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5386157
Reviewed-by: Thomas Nguyen <tungnh@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1286356}
--
wpt-commits: 7c2a090d60996315c82651c562aaea988d2220b5
wpt-pr: 45509
