Automatic update from web-platform-tests
[css-scroll-snap-2] Prioritize targets common to both axes (#44789)
Per step 6 of the proposal[1] to standardize snap point selection.
Improvements are made to the test files so that scrolling to set(s) of
aligned elements in one or both axes is supported and correctly handled.
[1]https://github.com/w3c/csswg-drafts/issues/9622#issue-2006578282
Bug: 323840955
Change-Id: I8ee234b6d5ae62329fdf12736ebef37ce685dc1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5296594
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268146}
Co-authored-by: David Awogbemila <awogbemila@chromium.org>
--
wpt-commits: 41e29a8e0b38e19aada34f0b8eabfe9a993cbe94
wpt-pr: 44789
Automatic update from web-platform-tests
Support header error debug reports for Attribution Reporting API
https://github.com/WICG/attribution-reporting-api/pull/1180
This CL introduces a new mojo method in AttributionDataHost mojo
interface to plumb the errors from header validation in the renderer to
the browser. This is necessary as the permission check for debug
reporting is performed in the browser, and also it helps to unify the
code path for errors from header validation in the browser.
Bug: 328043301
Change-Id: If8c0f1295dfc08d914138362c9275b0952b2e4b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5334963
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Brendon Tiszka <tiszka@chromium.org>
Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Nan Lin <linnan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268584}
--
wpt-commits: 11df0cd533436c33c98299fd9a52e2393d1cf21f
wpt-pr: 44904
Automatic update from web-platform-tests
Treat indefinite percentages in calc-size() calculation as 0.
This makes us correctly treat percentages in a calc-size() calculation
as zero in contexts where percentages are not definite.
Previously the tests I had for this passed because they were resolving
against -1 (kIndefiniteSize) and then the result was being clamped.
This adds a test (the "calc-size(any, 31% + 12px)" case) for a case
where that doesn't work correctly.
Bug: 313072
Change-Id: I37660a4c259cf02233d19659301f337077d30436
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5345509
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Auto-Submit: David Baron <dbaron@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268559}
--
wpt-commits: 1c839111fa1a7e1a06cbb359e89982f9cea5114b
wpt-pr: 44933
Automatic update from web-platform-tests
Use chromedriver to run WPTs with content_shell (#44868)
* Use chromedriver to run WPTs with content_shell
Use Chrome/WebDriver*Executor to run WPTs and drop
executorcontentshell.py.
Bug: 1295373
--
wpt-commits: 9be8c81d620080c6210417ee0eaacac609ca18b7
wpt-pr: 44868
Automatic update from web-platform-tests
[wptrunner] Add `infrastructure/expected-fail/` test for user prompts
This test exercises the handling of a testharness.js test that opens
user prompts like `window.alert(...)`. For WebDriver-controlled browsers
that default to "dismiss and notify", this should raise a harness error
in the executor's testdriver loop.
--
Cycle testdriver loop correctly
Otherwise, the executor, which expects a list, will fail to unpack
`None`.
--
wpt-commits: 0ee7a5af66cbe9c61a7db53cc35b8ecf6619286c, 7b6ef524a780c3d5f6b7c8d35ac03ddf03d97723
wpt-pr: 44489
Automatic update from web-platform-tests
Fix accessing update_properties for product
Now that we're passing around a Product class rather than a product
name, we don't need a separate `load_properties_update`, but can
straightforwardly just put `update_properties` directly on the Product
object we already have.
--
wpt-commits: eadc585217cba960e6bf94dba7018e690b3e8ac4
wpt-pr: 42839
Automatic update from web-platform-tests
Add historical test for navigator.getUserMedia
This is only non-normatively defined, thus we should hope that
implementations will not continue to surface it.
--
wpt-commits: 05c7ffcc945e53e819aed7d7c7c3d492886d845e
wpt-pr: 44909
Automatic update from web-platform-tests
Re-do close watcher user activation tracking
Our previous approach for close watcher user activation tracking had
cases where we could allow the cancel event to fire, but we were not
allowing it.
Fixing this is nontrivial. We need to more closely track the allowed
number of close watchers, and use it when making decisions about
creating ungrouped close watchers or firing cancel events. This allows
us to pass test cases like:
* A close watcher stack that is relatively empty compared to the amount
of user activations so far, needs to allow cancel events.
* A close watcher stack that is full compared to the amount of user
activations so far, needs to prevent cancel events.
Additionally, our previous mechanism of tracking groups by using
booleans on the close watchers was buggy when a close watcher was
destroyed. Instead, properly track the groups as a vector of vectors.
Spec PR: https://github.com/whatwg/html/pull/10168
Bug: 1512224
Change-Id: I6d7ccdc27c69f457455f517dcdbcc71d615b4290
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5232387
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268262}
--
wpt-commits: 01412b25ebfd1f389961cb6f733073e7d0b14dba
wpt-pr: 44828
Automatic update from web-platform-tests
Stop modifying author provided selection colors
CSS Issue https://github.com/w3c/csswg-drafts/issues/6150 was
resolved to require that browsers respect the author provided
colors in ::selection pseudos. Make the change.
Tested in unit tests and a WPT. Note that the default behavior
is not changed: chromium will still invert the color if the
text color matches the default selection highlight color.
Note the Mac layout theme was changed to return a non-transparent
color when the platform color is unavailable.
Bug: 40771258
Change-Id: I33fc8d18171da8b152f6e06a7f772b15f7175a16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5314122
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268136}
--
wpt-commits: 08b559de93d13573b1c5b42d238e069eebebcc56
wpt-pr: 44917
Automatic update from web-platform-tests
Document render blocking: remove "tentative" label
<link rel=expect> is now in the HTML standard, so no
need to be tentative.
Bug: 40948547
Change-Id: Ib58fb19c49ac470edbe270bff8b5cb0cb4f04c2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5340213
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268057}
--
wpt-commits: b6eff89db26583e020d2e6ca2bd4710993d568ac
wpt-pr: 44910
Automatic update from web-platform-tests
Avoid forced layout when finished parsing an empty subframe
The exiting check for empty document doesn't take into account that
we force-load an empty document, which doesn't change the flag.
Added a more appropriate check, initially behind the existing
kAvoidForcedLayoutOnInitialEmptyDocumentInSubframe flag, which would
allow us to finch-test this together with the previous change.
These two changes together should prevent jank on many sites that use
empty iframes, e.g. sites that use GTM.
This forced layout was overlooked by the previous test because it
doesn't use the proper code path for forcing layout. Updated the test
to ensure that added nodes don't have their styled clean (they still need a style recalc) after adding the iframe to the DOM.
Also two existing tests rely on the current behavior to pass:
1) third_party/blink/web_tests/fast/frames/avoid-forced-layout-on-empty-subframe.html
The extra layout was masking another bug, where an extra layout is
needed to correctly layout a select box with content-visibility:hidden.
(crbug.com/327723279)
2) chrome/test/data/webui/new_tab_page/logo_test.ts
This tests that doodles in the "new tab page" respond to resize requests
by animating the width/height of an empty iframe. Added a wait of one
animation frame to ensure the initial state of the iframe is rendered
rather than rely on that coincidental forced layout.
Bug: 324572951
Change-Id: Ib3b50e330e9a72c83b29d1e47f256b7ce33ae8ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5335144
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1268096}
--
wpt-commits: 11c2ded178a8f34d968041a7a4a2493b57d30ed3
wpt-pr: 44879
Automatic update from web-platform-tests
Implement context-fill and context-stroke SVG paint properties
The change to the existing WPT is to address:
https://github.com/web-platform-tests/wpt/issues/44771
Bug: chromium:40362923
Change-Id: I5f67b0e98f0f322d8a68e2e2e46ad64bc8d2b30e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5322726
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267998}
--
wpt-commits: 9359c609fc260311dd33a1bff3c2da6e6ad2fdc7
wpt-pr: 44773
Automatic update from web-platform-tests
IDB: Consolidate previously extended WPT files into one.
Consolidate 16 test files related to idbobjectstore_add into one file.
These tests were previously extended to cover dedicated, shared &
service workers, but were spread across multiple files. All tests
consolidated to one file: idbobjectstore_add.any.js
Bug: 41455766
Change-Id: Ic4ea248ea8d427b7d657c77cc462062a0a895a51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5334102
Commit-Queue: Sneha Agarwal <snehagarwal@microsoft.com>
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267991}
--
wpt-commits: 1c3f16b38ea8f6825bc11a2f10cfa6551c154d64
wpt-pr: 44844
Automatic update from web-platform-tests
[ProtectedAudience] Add more generateBid() browserSignals tests.
In particular, make sure that bidCount and prevWins are updated or
not as appropriate in the following cases:
* Interest group bids but another group wins the auction.
* Interest group bids but the seller rejects all bids.
* Interest group bids but the seller throws an exception.
* Interest group does not bid.
Add the following tests for bidCount only (they're just less interesting
for prevWins, though could test it in that case, too)
* Interest group does not bid, but another group does and wins the
auction.
* Interest group bids but the seller rejects the bid,
and another interest group wins the auction.
Also add a prevWins test where two auctions are run at once (matching
a pre-existing bidCount one), and the unique test case:
* Interest group bids but the seller gives the bid a low score,
and another interest group wins the auction.
Bug: 40261114
Change-Id: Ib3ea5e9bc78b058dccd91986b0c59ee46a263ad4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5323808
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Commit-Queue: mmenke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267987}
--
wpt-commits: 888f5d7e1849113d06ec861ae5c7a04e59a92e66
wpt-pr: 44837
Automatic update from web-platform-tests
Add layers variant to remaining filter tests
Modified the existing generated tests that apply filters via
`CanvasFilter` objects, to also generate variants that apply them via
layers.
These remaining tests did not require a significant redesign. The
variant that uses layers work in the same as the existing tests, just
adding the required `beginLayer` and `endLayer` calls.
Bug: 1396372
Change-Id: I381c2938f30cc68f9778adeae05bb7e58e4ba6c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5225024
Reviewed-by: Jean-Philippe Gravel <jpgravel@chromium.org>
Commit-Queue: Andres Ricardo Perez <andresrperez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267892}
--
wpt-commits: c9cfe944065a4688bb94e87bca13d1d69689e266
wpt-pr: 44911
Automatic update from web-platform-tests
[Grid] Fix overlapping grid-area regression
In https://chromium-review.googlesource.com/c/chromium/src/+/5148190, I
added a condition that was too aggressive in excluding inherited grid
areas.
This change loosens that condition and adds a test for the missed case.
Bug: 327499436
Change-Id: I71a7185795fb8071a247218080f337085827376e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5336611
Reviewed-by: Alison Maher <almaher@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1267974}
--
wpt-commits: 1826711d3471c740e544a43a7d60d7df9afb474a
wpt-pr: 44895
Automatic update from web-platform-tests
Workaround to deflake 3PC heuristics WPT.
Firefox is flaky on both assertions for default 3PC access. Force-failing the test to avoid calling these flaky assertions until Firefox implements them. (We don't want to force-succeed as it will hide the test which is tentative but should be implemented.)
Bug: 326123298
Fixed: 326123298
Change-Id: Ic2bd69549a746452cea24fc9c77cec39c575bd26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5322658
Reviewed-by: Joshua Hood <jdh@chromium.org>
Commit-Queue: Anton Maliev <amaliev@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267950}
--
wpt-commits: 856230102b1945fca46816673890549fbe009c51
wpt-pr: 44875
Automatic update from web-platform-tests
[wdspec] fix test for `contexts` fields in add_intercept (#44859)
* [WebDriverBiDi] Proper test for `contexts` fields
* chore: fix
--
wpt-commits: 4a4a7b84e2f64dadc59f3d3704aed4cb55eb6f99
wpt-pr: 44859
Automatic update from web-platform-tests
Add layers variant and references to componentTransfer tests
Modified the existing generated tests for the `componentTransfer`
filter, to also generate variants that apply them via layers.
The existing tests used asserts on pixel data. They were converted into
reference tests by drawing all the required rectangles in different
positions in the canvas.
Bug: 1396372
Change-Id: I10fa22dbcfb466a07ce3d82013caed70be4c4491
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5225022
Reviewed-by: Jean-Philippe Gravel <jpgravel@chromium.org>
Commit-Queue: Andres Ricardo Perez <andresrperez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267886}
--
wpt-commits: 63d1b04acc3fd2aebeb8973f18c625c7fd3b8773
wpt-pr: 44866
Automatic update from web-platform-tests
<link rel expect> should only work with light DOM
Don't let elements in shadow DOM unblock rendering.
Bug: 327254055
Change-Id: If668f144103ce58d6ea66992f53637ee1ce728d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5331635
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267900}
--
wpt-commits: 9a5783669bcdf224fb89beb6f1d7c71d3981a417
wpt-pr: 44839
Automatic update from web-platform-tests
Add layers variant to colorMatrix filter tests
Modified the existing generated tests for the `colorMatrix` filter, to
also generate variants that apply them via layers.
Bug: 1396372
Change-Id: Id5ae567ec9470db24d043416e4e263fe6f9bfecc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5213971
Reviewed-by: Jean-Philippe Gravel <jpgravel@chromium.org>
Commit-Queue: Andres Ricardo Perez <andresrperez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1267878}
--
wpt-commits: 6a6bbbfed27c43a522aeb2dd3013c84b73c48338
wpt-pr: 44121
This basically makes the macOS behave the same as other platform (currently only
macOS would read data from clipboard cache). And also this would ensure behavior
doesn't change if one day we would like to enable reading-from-clipboard-cache
on other platforms as well.
Differential Revision: https://phabricator.services.mozilla.com/D203893