And alias :-moz-ui-valid and :-moz-ui-invalid to them.
There are CSSWG resolutions for these for quite a while, and spec for
user-invalid.
Differential Revision: https://phabricator.services.mozilla.com/D105966
Automatic update from web-platform-tests
[layout] Don't allow non-formatting-context to be relayout-roots.
As lots of state can be passed from a non-fc to its sibling, treating
these as formatting context roots is incorrect for lots of edge cases.
This patch dis-allows non-fcs to be relayout-roots.
Change-Id: Ieef1a2ad1d653bd954a8a9989aecc8ac83107f69
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2707136
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856317}
--
wpt-commits: dfe483887469f2ad966d6244910b7aa5f0cfbb7b
wpt-pr: 27710
Automatic update from web-platform-tests
Update ResourceTiming style guide to explain asserts vs. errors
In ResourceTiming Web Platform Tests, we want to use assertion failures
to indicate divergence from the spec but use exceptions to indicate
issues with the test code.
This change updates the style guide to call out this goal.
Bug: 1171767
Change-Id: If9df3b05de75cbb516bc5c9f1ac0897abac0b4ab
GithubIssue: https://github.com/w3c/resource-timing/issues/254
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2707184
Commit-Queue: Tom McKee <tommckee@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856285}
--
wpt-commits: 33d176b3b6f0e85351afd41f3f88db97afc4b509
wpt-pr: 27707
Automatic update from web-platform-tests
[COOP] access reporting: fix flakes reporting.html (#25834)
---
The WPT testharness.js is defining:
```
WindowTestEnvironment.prototype._forEach_windows = function(callback) {
// Iterate over the windows [self ... top, opener]. The callback is
// passed two objects, the first one is the window object itself, the
// second one is a boolean indicating whether or not it's on the same
// origin as the (...)
```
This causes some postMessage to be sent cross-window. They are reported
and causes failures. For instance in reporting-observer.html test.
This patch removes testharness.js from executor.html
This fixed the issue for reporting-observer.html
More generally, we shouldn't check access in between two windows, when
one of them is using testharness.js
---
Second discovery:
The official web-platform-test runner sometimes drop POST requests
when many are requested in parallel. Using a lock fixes the issue.
---
Bug: 1090273
Change-Id: I261b9bfece935e3613c250a3a9402a1c8a6ff14e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436742
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855712}
Co-authored-by: arthursonzogni <arthursonzogni@chromium.org>
--
wpt-commits: 9b505f9fc3dd45db0fb084de8bbc86a120763904
wpt-pr: 25834
Automatic update from web-platform-tests
Test "scale" where x == y but z != 1, to make sure that y is not dropped.
--
wpt-commits: f2791b72df36027cf169e009f21a7b2bfdfd3f45
wpt-pr: 25961
Automatic update from web-platform-tests
[css-backgrounds] Add test ensuring border-image is displayed with a transparent border-color
--
wpt-commits: acfda5e29a50a895d0b2ff9038158e43e3c0b19f
wpt-pr: 26350
Automatic update from web-platform-tests
Add test to measure which WebRTC stats are provided at all
Based on similar test for Mandatory-To-Implement stats in WebRTC
--
wpt-commits: f40c6991aad41bef4f576d6005575bf1216082d4
wpt-pr: 27571
Automatic update from web-platform-tests
HTML: <tr height=0> is a thing
See https://github.com/whatwg/html/issues/4716.
--
wpt-commits: dae12631cf61e719048871f90f4f6e4e451c526d
wpt-pr: 17571
Automatic update from web-platform-tests
Make SubresourceWebBundles feature available only in Secure Context
We are developing the SubresourceWebBundles feature behind the feature
flag. This feature is enabled when
--enable-features=SubresourceWebBundles or
chrome://flags/#enable-experimental-web-platform-features is enabled
even when the page is non-Secure Context.
But according to this doc, we should make powerful new features
available only to secure origins.
https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features
So this CL makes the SubresourceWebBundles feature available only in
Secure Context by:
(1) Add [SecureContext] extended attribute to `resources` and `scopes`
attribute of HTMLLinkElement in html_link_element.idl.
(2) Check IsSecureContext() also when we check
RuntimeEnabledFeatures::SubresourceWebBundlesEnabled().
Note: this restriction doesn’t affect Origin Trial of this feature,
because Origin Trials are only enabled for secure origins.
Bug: 1082020
Change-Id: Ifa533f99f64c83015d293946084395a5af59cfba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2703194
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856177}
--
wpt-commits: 4fc6cf99aedf93fab4516c19372f937e636059f7
wpt-pr: 27674
Automatic update from web-platform-tests
Add a test to check "Sec-Fetch-Dest: webbundle" header is present
A request for a bundle should have a "Sec-Fetch-Dest: webbundle"
request header with the <link>-based API.
This CL adds a test to make sure that the current implementation is
correctly sending the header.
The PR for the explainer is https://github.com/WICG/webpackage/pull/626.
BUG=1149816, 1168449
Change-Id: I2bc85be77d45044e9362dd5b998a92743e93eaa5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2706327
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856164}
--
wpt-commits: 8d3bafb23256c51e76618b849e73f960c32767ed
wpt-pr: 27695
Automatic update from web-platform-tests
Simulate user inputs in css-scroll-snap/snap-at-user-scroll-end.html
Use testdriver Action API to simulate wheel scroll actions in
css/css-scroll-snap/snap-at-user-scroll-end.html.
Bug: 1145677
Change-Id: I98e121d71257c2f64244bfee48821fc65a988097
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569986
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856129}
--
wpt-commits: 7af9d6ec48ab04043a2bea85a3599904a1a19efa
wpt-pr: 27373
Automatic update from web-platform-tests
Change request's mode to reflect the WebBundle explainer's change
Reflect the change of the WebBundle subresource loading explainer in
https://github.com/WICG/webpackage/pull/622.
Request for a bundle will have its mode set to "cors" and its
credentials mode set to "same-origin" unless a crossorigin attribute
is specified.
BUG=1149816, 1168449
Change-Id: Ie836e77fd50524b4019283d5237aec70cc29433b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2703299
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855997}
--
wpt-commits: 7cbccf70c5a4a7f4d4113057696228f49de48008
wpt-pr: 27692
Automatic update from web-platform-tests
Light-dismiss <popup>s on scroll
This adds light-dismiss behavior for scrolling actions to the <popup>
implementation. It is important to dismiss popups when scrolling,
because the eventual implementation of anchor positioning will be
performance-limited if positions need to be computed while scrolling.
Bug: 1168738
Change-Id: Icdc876121c42b9518633166531cca56602b54382
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2707385
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855925}
--
wpt-commits: 726c26673655f1d1c9989c4d122eef3930100f27
wpt-pr: 27709
Automatic update from web-platform-tests
Children of MathML containers always establish a new FC.
Just like flex and grid items, children of MathML containers establish a
new formatting context. When falling back to legacy layout at a
descendant, stop legacy fallback propagation at such ancestors (since
they cannot be laid out by the legacy engine - no implementation there).
Add a DCHECK to catch such problems earlier (rather than in layout).
This also fixes a similar issue for css-layout-api, unless we make an
extra effort not to fix it. :) So added a test that used to DCHECK-fail
in the exact same way.
Bug: 1178979
Change-Id: Ib76cdc226147c454c4e3de91a300af1295e8aa35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2705086
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855879}
--
wpt-commits: 424adee45347220d696b79fd410933ed8631a5b3
wpt-pr: 27711
Automatic update from web-platform-tests
Py3 fixes for VCS syncing (#27706)
These changes address various errors that are currently preventing Servo's nightly downstream sync of WPT from completing.
--
wpt-commits: 1b484b247dd26a364a40b43ee79946c3f38c45e3
wpt-pr: 27706
Automatic update from web-platform-tests
[CompositeAfterPaint] Handle main thread scrolling change during scroll animation
In pre-CAP the situation is handled when composited scrolling layer
changes in CompositedLayerMapping during compositing assignments update.
Not sure how a mere main thread scrolling status change (e.g. adding
background-attachment:fixed to a composited scrolling scroller) is
handled, but a test for the situation passes.
For CAP, now check change of main thread scrolling status in
PaintPropertyTreeBuilder.
The original test for the situation has not been working since we
removed rounded corner as a blocker of composited scrolling. Fix and
modernize it and add wpt tests.
Bug: 1176543
Change-Id: I00595635a7b1a729ddd05173e3452e40c34e52b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2688140
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855835}
--
wpt-commits: 4c56f3ec2751ff5952b317be7e40844c7b6cf914
wpt-pr: 27648
Automatic update from web-platform-tests
[css] Make frameset include border/padding in its intrinsic width
It tripped a DCHECK in flex.
Fixed: 1173843
Change-Id: I489cd30e54333e4b2c381e240324fd7145bcd406
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2705814
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855824}
--
wpt-commits: 206391ea7af599d112b15a3d8c2dbb4c593f291f
wpt-pr: 27690
Automatic update from web-platform-tests
Do not change referrer policy on document.open
At the moment on document.open chrome sets the referrer policy of the
opened document to be equal to the referrer policy of the
entryDocument. This CL removes this step, keeping the previous
referrer policy instead.
Fixed: 1174496
Bug: 1130587,1174496
Change-Id: Ica4740bbd2baed0ca5bb6770c3c38132573eb374
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2674927
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855766}
--
wpt-commits: 211f1f94e7e1996a3f6cb8b91fb16d4fc4b87d0b
wpt-pr: 27563
Automatic update from web-platform-tests
new parameter --include-file for wptrunner (#27636)
* new parameter --include-file for wptrunner
Add new command line parameter --include-file for wptrunner,
so that we can load test cases from a file.
--
wpt-commits: 1d2b75901ed1158d557695c58294ac5f78bd492e
wpt-pr: 27636
Automatic update from web-platform-tests
[Credentialless] WPT fetch
1. Add the base WPT directory for testing cross-origin-embedder-policy
credentialless:
/html/cross-origin-embedder-policy/credentialless/
2. Add one test about fetch. A few parameters can vary:
- Initiator is COEP:none or COEP:credentialless
- Request url is same-origin or cross-origin.
- Request mode is no-cors or cors.
- Request credential is 'same-origin' or 'include'
Bug:1175099
Change-Id: Id1565735e895dabbfd7f098df03cecfc0c185b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2667352
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855725}
--
wpt-commits: 42520aee44d600c98a5495aba5fe5bfcba694fc6
wpt-pr: 27525
Automatic update from web-platform-tests
[selectors] Improve focus-visible-011.html
Some improvements on this test:
* Call preventDefault() for keydown, keyup and keypress events
(so if an implementation relies in one of them it'll fail).
* Use a DIV instead of a BUTTON, so it can be run on Mac platforms too
(buttons don't get focused on Mac in WebKit and Firefox).
--
wpt-commits: d9effa0e3d86deb2b91bd050c540afa6e7e2a436
wpt-pr: 27700
Automatic update from web-platform-tests
[python3] Remove six usage from tools/wptserve/
--
[python3] Remove most usages of six from wptrunner
--
wpt-commits: e96b794871b38cbf459b29aef3c2709acc3e25a8, d4eabb98ff452bb209b93a780abc242ba55615fb
wpt-pr: 27480
Automatic update from web-platform-tests
Consider the hyhen size in the available width when evaluating overflow
The logic in NGLineBreaker::BreakText completes the algorithm by
evaluating whether the NGInlineItem inline size fits in the available
width, received in the function argument "available_width".
However, when hyphenation is applied, we reduce this initial available
width, subtracting the hyphen inline size, and run another iteration of
the ShapeLine() function. The new item's inline size is evaluated again
to check whether it overflows or not.
The root case of the issue described in the bug is that we are using
the value stored in the available_width variable, which we've just
reduced because of hyphenation. We should use the
available_width_with_hyphens variable instead.
Bug: 1175716
Change-Id: I3ecac2362f7cf9951cd0d323a7b163385d240f89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2704079
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855647}
--
wpt-commits: 7550407f4cfcf8368f12858ad0e9800887c8ee22
wpt-pr: 27677
Automatic update from web-platform-tests
Add manual wpt test for clipboard files
Add new wpt/clipboard-apis/clipboard-file-manual.html test, and update
wpt/entries-api/* tests to work with both drag-and-drop, and copy-paste.
Bug: 1175483
Change-Id: I5d099bdd3bab616886dcc549b3e4c5b197271308
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2695188
Commit-Queue: Joel Hockey <joelhockey@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855614}
--
wpt-commits: 3d345fd2a1e43595e20af547b11e7b65bbebefc3
wpt-pr: 27627
Automatic update from web-platform-tests
Introduce <selectmenu> with basic shadow structure and some controller code
Begin implementing the <selectmenu> element, a version of <select> with
a fully author-customizable UI.
See https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/9TcfjaOs5zg/m/WAiv6WpUAAAJ
and associated links for additional context.
Establish the basic shadow DOM structure, with a button (which
includes an arrow icon and a container to show the value), and
a listbox based on <popup>. There are <slot> elements to add
<option>s to the popup and replace any of the default parts.
Include some basic styles. The default button part looks something
like the native <select>, but the default listbox will need more
work to improve its appearance.
Add basic controller code using NativeEventListeners. Clicking
the button part opens the listbox <popup>, and the value property
and text shown in the button are updated when an option is clicked.
This controller code is applied to the default parts and to
author-supplied parts that are included via the <slot>s.
Add tests to validate some basic scenarios involving the
controller code. Note, a couple of the
selectmenu-value.tentative.html
tests fail because updates to the value property are not yet
synchronous (should they be?).
There are many TODOs and open questions to investigate, but
this change establishes a starting point for exploring
an approach to customizable form controls.
Bug: 1121840
Change-Id: I68c0513b0e30813cbaa3b69fc2acb9086c7400ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2693857
Commit-Queue: Dan Clark <daniec@microsoft.com>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Ionel Popescu <iopopesc@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#855581}
--
wpt-commits: 6ba9b6bb71afb574b48982a6bffee37051b833f6
wpt-pr: 27623
Automatic update from web-platform-tests
Add more position modes to <popup> test
The existing test just made sure that position:absolute worked with
an overflow:hidden ancestor. This adds position:fixed (default) and
position:relative. Just to make sure.
Bug: 1168738
Change-Id: I2ad18ea2f41d0c7310098a6ab5535263fce773c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2704734
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855558}
--
wpt-commits: 061aa7690a61d7afaf4028f26034d8e9d03e28cb
wpt-pr: 27689
Automatic update from web-platform-tests
Replaced start and end scroll offsets with scrollOffsets attribute
Based on pr[1] replaced all usages of startScrollOffset and
endScrollOffset with scrollOffsets attribute.
Among the changes;
-Moved content of constructor.tentative.html to constructor.html.
-Deleted constructor.tentative.html
[1] https://github.com/w3c/csswg-drafts/pull/5803
Bug: 1094014
Change-Id: I3d609555bdd7c65b2b9561a88d4c130a5566a9a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2701333
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#855469}
--
wpt-commits: 69bf427d7d2ae83f7c60ef6751ddf0e26d2892fa
wpt-pr: 27665
Automatic update from web-platform-tests
Add websockets and iniconfig to tools/localpaths.py
--
Add pytest from pip directly
Use git add -f tools/third_party/pytest to include version file.
This includes _version.py and pytest.egg-info folder.
--
Add pytest-asyncio to tools third_party
--
Add pytest-asyncio to localpaths
--
Add a test for WebDriver capabilities for webSocketUrl
Test establishing a Bidirectional Session capability support
--
Add an async style test for connecting to WebDriver
Test connecting to WebDriver session using websockets
and send a message in async/await style
--
Add BidiSession class and tests using modified session fixture
1. Added a BidiSession class in bidi.py under tools/webdriver/webdriver
that will preset capability for websocket connection.
Created async versions of start and end for the class to handle
establishing and closing websocket connection.
2. Modify session fixture to take an extra boolean argument "bidi"
for creating bidi session. Change the fixture to async and use
await when dealing with bidi session start/end.
3. Set event loop scope to session(assuming it would reuse the same
event loop for all tests) to avoid event loop is closed error when
closing websocket connection.
4. Added tests for different bidi/classic session creation scenario
and tested connect/send/close.
--
Import localpaths in resources/test/conftest.py
--
Moved bidi test to its own folder
--
wpt-commits: 8674fbf718d0878c4d467801cb34aa7c0a0b4d31, 514df5671398fda1bd43fb91d83421d76c09110f, e78b6538d0703d8e9e10f8a61d14e6be81c16d11, 32b9de9873b0f4f69dfead82490097d742f33cf4, 21e149dd13cc951c68ac282d42e2eeeff145e13b, 661a05e4467eb3219e23b1a8cd119e04f82da668, 9fad072d48bbda7b44bcd93df5d542afcd5f9e1c, e366371a194459f23f8d6115cfdb57e0bc851468, def808ad0f4c39bbea9b7e8555fa474c7d54b45c
wpt-pr: 27195
Automatic update from web-platform-tests
Add WebGL tex(Sub)Image(2D|3D) support for WebCodecs VideoFrames.
This expands the same interfaces used for HTMLVideoElement with WebGL so
they work with the WebCodecs VideoFrame. This is pretty much an exact
clone of what we do for the video element, but condensed into one
function without the caching which happens in WebMediaPlayer's
longer-lived media::PaintCanvasVideoRenderer.
Bug: 1175907
Test: New WPT tests.
Change-Id: Id8604a35bd11e18e100360c2bdced1418598f1fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2692495
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855425}
--
wpt-commits: e73ee12344b919c1c81c02fdec3a8c13ef7071e2
wpt-pr: 27619
Automatic update from web-platform-tests
Avoid DCHECK in HTMLSelectElement::SetOption
SetOption adds a new <option>, but in some unusual cases, the <option>
can be a parent of the <select> which it is getting added to, which
prevents the <option> from being appended to the <select>. This adds a
check to the ExceptionState which reflects the failure to append instead
of continuing on assuming that the <option> was successfully appended.
Fixed: 1178128
Change-Id: Ibfc04c2d4eb672fa2d7695855ffd8ca3d773337b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2704645
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855411}
--
wpt-commits: 9b7fac08b053897d5b60337ffd9811c9d380e3a3
wpt-pr: 27684
Automatic update from web-platform-tests
[advance-override] Rename advance-proportional-override to advance-override
This is the follow up of crrev.com/c/2702291
Now that the CSSWG has standardized a descriptor 'advance-override' [1],
which works exactly the same as the 'advance-proportional-override', this
patch renames it to 'advance-override' to match the spec.
There's also a test moved from wpt_internal to wpt since it has been
standardized now.
[1] https://github.com/w3c/csswg-drafts/pull/5991
Bug: 1137633
Change-Id: I85d8cc5e3fef0315c36d1436cb21f1d4be85b04b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2702477
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855390}
--
wpt-commits: 7e4c574291142087f00efa00f782be03cebda75a
wpt-pr: 27668
Automatic update from web-platform-tests
Add a test that clipping doesn't affect <popup>
Just a quick test that a parent container can't clip the
display of <popup>.
Bug: 1168738
Change-Id: If9e0f498495bae1e0cdd2da76cfc16cf31cffb09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2702375
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855388}
--
wpt-commits: 1809c557eb2ace7b1e1f8c1e1c7e3467d56c4a56
wpt-pr: 27682
Automatic update from web-platform-tests
Resnap to focused element after relayout (#27683)
--
wpt-commits: ec07c2477860546cb3cdbc0f8070798d65b4af0d
wpt-pr: 27683
Automatic update from web-platform-tests
Reland "Add drawImage() and createImageBitmap() support for blink::VideoFrame."
This is a reland of 27830868be3b06b19761c7ca4507a8e77ab1f535 - Actual
culprit was https://crrev.com/c/2698301
Original change's description:
> Add drawImage() and createImageBitmap() support for blink::VideoFrame.
>
> This makes blink::VideoFrame a CanvasImageSource for drawImage() and
> wires up the existing ImageBitmapSource implementation to
> createImageBitmap() to deprecate VideoFrame.createImageBitmap().
>
> A deprecation notice is added for VideoFrame.createImageBitmap(); the
> method will be removed prior to shipping WebCodecs.
>
> Bug: 1175907
> Test: New (moved from internal) WPT tests.
>
> Change-Id: I549d996c9b16a8d0a1dd5293b5bee29f61cac8f3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2680955
> Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Reviewed-by: Fernando Serboncini <fserb@chromium.org>
> Reviewed-by: Jeremy Roman <jbroman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#854938}
Bug: 1175907
Change-Id: Iecd29b081b9fd70e31836fdace7b0c9f4ab60aca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2702518
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#855343}
--
wpt-commits: 9401b76892788ec7ebcfbffc26dcf09ed64c253a
wpt-pr: 27669
Automatic update from web-platform-tests
Test cases where request body gets used before network fallback (#27325)
Tests for whatwg/fetch#1144 and w3c/ServiceWorker#1563.
Co-authored-by: Yutaka Hirano <yhirano@chrmomium.org>
Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
--
wpt-commits: c30545df6a50c61f3673ed952c78c0a607100d45
wpt-pr: 27325
Automatic update from web-platform-tests
Revert "Add drawImage() and createImageBitmap() support for blink::VideoFrame."
This reverts commit 27830868be3b06b19761c7ca4507a8e77ab1f535.
Reason for revert: New tests SEGVing on several linux bots
Original change's description:
> Add drawImage() and createImageBitmap() support for blink::VideoFrame.
>
> This makes blink::VideoFrame a CanvasImageSource for drawImage() and
> wires up the existing ImageBitmapSource implementation to
> createImageBitmap() to deprecate VideoFrame.createImageBitmap().
>
> A deprecation notice is added for VideoFrame.createImageBitmap(); the
> method will be removed prior to shipping WebCodecs.
>
> Bug: 1175907
> Test: New (moved from internal) WPT tests.
>
> Change-Id: I549d996c9b16a8d0a1dd5293b5bee29f61cac8f3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2680955
> Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Reviewed-by: Fernando Serboncini <fserb@chromium.org>
> Reviewed-by: Jeremy Roman <jbroman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#854938}
Bug: 1175907
Change-Id: I41b3cc7e6d76e4c80131d8cad2299774e4ebec95
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2702757
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#855005}
--
wpt-commits: d614b23de08adf12271dcdca27fe752bc4c6a952
wpt-pr: 27667
Automatic update from web-platform-tests
Allow fragmentainers with zero block-size.
The spec [1] says that fragmentainers are assumed to have a minimum
block-size of 1px regardless of their used size, in order to guarantee
content progress. We implemented this by simply making sure that the
used block-size of a fragmentainer would never become less than 1px. But
this wasn't ideal, as that would contribute to unwanted layout overflow
in cases where the content of the multicol container was shorter than
1px.
We'll now still accept at least 1px of content into each fragmentainer,
but don't stretch the fragmentainer itself (just allow the actual column
fragments to become that short as they want, and instead let the content
overflow the columns if necessary).
We still need to fill at least 1px of content before moving to the next
fragmentainer, and fast/multicol/zero-height-with-children.html is a
good test for this.
[1] https://www.w3.org/TR/css-break-3/#breaking-rules
Bug: 829028
Change-Id: I7b4e69524288dad8bb10fd10c715339d1769815a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2698554
Reviewed-by: Alison Maher <almaher@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854974}
--
wpt-commits: dfa6dff98df467e0fa2721833c54f7a538d10158
wpt-pr: 27660
Automatic update from web-platform-tests
[TableNG] Fix saturated sizes issue.
We can end up in a situation where:
- table_inline_size is at LayoutUnit::Max()
- border_padding.InlineSum() is at LayoutUnit::Max()
- border_spacing.inline_size is some small value.
This combination results in a negative section_available_inline_size.
Bug: 1178044
Change-Id: I3bd860033195ed420323445e1c790d9f59962b98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2694345
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854940}
--
wpt-commits: 806ae8875bea1b8380081b0da8fd416337ea447f
wpt-pr: 27622
Automatic update from web-platform-tests
Add drawImage() and createImageBitmap() support for blink::VideoFrame.
This makes blink::VideoFrame a CanvasImageSource for drawImage() and
wires up the existing ImageBitmapSource implementation to
createImageBitmap() to deprecate VideoFrame.createImageBitmap().
A deprecation notice is added for VideoFrame.createImageBitmap(); the
method will be removed prior to shipping WebCodecs.
Bug: 1175907
Test: New (moved from internal) WPT tests.
Change-Id: I549d996c9b16a8d0a1dd5293b5bee29f61cac8f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2680955
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854938}
--
wpt-commits: 5eb4f915be3924ab711150454b1fe083a685e620
wpt-pr: 27617
Automatic update from web-platform-tests
[AspectRatio] Take box-sizing into account in replaced element intrinsic sizing
Take box-sizing into account in replaced element intrinsic sizing when
using aspect-ratio, but keep using content-box when resolving
width/height when no aspect-ratio is set.
This CL removes ResolveWidthForRatio/ResolveHeightForRatio functions
and instead uses InlineSizeFromAspectRatio/BlockSizeFromAspectRatio.
Finally code is added to handle non horizontal writing-mode and a test
is added for that.
Bug: 1163176
Change-Id: I28449b3a0f567d4b3e41afe9a7429a0b03250fb3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2690332
Commit-Queue: Rob Buis <rbuis@igalia.com>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854925}
--
wpt-commits: c9da3535ef3eb8ad5c24a7c5812e68ac3359ba86
wpt-pr: 27613
Automatic update from web-platform-tests
Fix touch-events/single-touch.html on WPT dashboard
On WPT dashboard, touch-events/single-touch.html fails because touchmove
and touchend events are not received. I fixed this test, so we can now
receive all the touch events.
https://wpt.fyi/results/touch-events/single-touch.html?
label=experimental&label=master&aligned
Bug: 1163370
Change-Id: If0b2ca65d597c89ad982ea51f80e7d026c8a72e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2689949
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854921}
--
wpt-commits: 618b27ffa120cc7c5a576b6375954c9fb42c36a9
wpt-pr: 27663
Automatic update from web-platform-tests
[TablesNG] Fix orthogonal cell sizing crash.
In order to pick up the fallback orthogonal size we need to call
SetAvailableSize on the builder.
This was triggered after some logic tightening within ng_length_utils.
Bug: 1178130
Change-Id: I59d1c4c9882d96a558e035daa07debb80283fa9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2694344
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854893}
--
wpt-commits: 7198e2d0ff453d9d2ff1622dee4bd08be2ba7224
wpt-pr: 27621
Automatic update from web-platform-tests
[AspectRatio] treat <ratio> that ends with slash as invalid
Treat <ratio> that ends with slash as invalid:
https://drafts.csswg.org/css-values-4/#ratio-value
Bug: 1045668
Change-Id: Icc4c16222f89402958b7e9f01c904472b15cfa80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2697151
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#854815}
--
wpt-commits: 2ebf73585d4644cc5f232184b69642f36b6b8344
wpt-pr: 27649
Automatic update from web-platform-tests
[selectors] Use ENTER instead of SHIFT in focus-visible-007.html
It's not clear if a modifier key like SHIFT implies
that "the user interacts with the page via the keyboard".
Using ENTER key instead of SHIFT it seems everyone agree,
so let's change the test to use ENTER.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1688539.
--
wpt-commits: 1bee46095eea9411a13783fba4cb08bffbdc8af2
wpt-pr: 27656
Currently the default value of buttons is set to
MOUSE_BUTTONS_NOT_SPECIFIED, which defers calculation of the value to
the DOMWindowUtils GetButtonsFlagForButton function. This calculates a
default value based upon the value of the button key.
By specifying a default button value of 0, which has a meaning of
ePrimary, the buttons value is calculated as the
ePrimaryFlag (1), suggesting that a button was pressed.
This patch changes the behaviour to set the value of buttons based on
the original value of button before the default was applied. The value
of buttons also considers the event type to ensure that a mousedown
event has a default value calculated by DOMWindowUtils.
With the new behaviour:
- if a value was explicitly set for buttons, this is used
- if a value was explicitly set for button, then the not-specified
constant is used to defer calculation to DOMWindowUtils
- if an event type was specified and that event type was not the
'mousedown' event, then the no-button constant is used
- if an event type was not specified or it was for the 'mousedown'
event, then the not-specified constant is used to defer calculation to
DOMWindowUtils
Differential Revision: https://phabricator.services.mozilla.com/D105877
This patch enables the faster mix-blend-mode path that allows using
picture cache tiles as the backdrop source for blends where that
is appropriate (most of the underlying work is in previous patches
or the dependencies of this bug).
In addition to avoiding an extra intermediate surface for blends
that are on a picture cache surface, it also avoids constant
invalidation of picture cache tiles due to the blend container
not being part of the main content scroll root.
As an example of the typical performance improvement, the GPU times
on an AMD 5700 GPU at 4k, when using the Firelux color temperature addon
browsing pages drops from ~1.8ms to ~0.3 ms.
Differential Revision: https://phabricator.services.mozilla.com/D104491
This will allow to upgrade the underlying docker image independently.
The resulting binary has been verified to be identical bit for bit.
Differential Revision: https://phabricator.services.mozilla.com/D105714
Automatic update from web-platform-tests
Simulate user inputs in wpt/touch-events/multi-touch-interfaces.html (#27401)
Use testdriver Action API to simulate touch actions in
third_party/blink/web_tests/external/wpt/touch-events/
multi-touch-interfaces.html.
This test is newly imported from WPT repository.
Bug: 1145677
Change-Id: Ib8c6a43a769347c91ba28155d8405a0e90cebc49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2641006
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852297}
Co-authored-by: Lan Wei <lanwei@chromium.org>
--
wpt-commits: 2b1a71a1bb6165fc1b64a29469b3983e8c8cacb1
wpt-pr: 27401
Automatic update from web-platform-tests
Increase timeout of openSXGInIframeAndWaitForMessage (#27637)
Some tests which use openSXGInIframeAndWaitForMessage() fail on mac
10.15 debug bots. This is because the debug binary is very slow.
So loading a cross origin iframe that requires a new process takes
longer than 3000 ms.
This CL changes openSXGInIframeAndWaitForMessage() to use 10 sec timeout
same as service-workers/service-worker/fetch-frame-resource.https.html.
And also adds <meta name="timeout" content="long"> tag in some tests
where the iframe load is expected to fail.
Bug: 1177883
Change-Id: Iee8a94bddf58d5f9a8113f30c14cff43a6119d95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2694296
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854144}
Co-authored-by: Tsuyoshi Horo <horo@chromium.org>
--
wpt-commits: 2037343af04e732a3b21cf1e1ae2589a97931cc9
wpt-pr: 27637
Automatic update from web-platform-tests
Check serving constraints of WebBundle responses
This adds check for the serving constraints of WebBundle responses [1].
After this patch, subresource web bundles served without the following
response headers will be rejected.
- Content-Type: application/webbundle
- X-Content-Type-Options: nosniff
[1] https://wicg.github.io/webpackage/draft-yasskin-wpack-bundled-exchanges.html#name-serving-constraints
Bug: 1176493
Change-Id: I03adef6bad769dfd69fdad76c933f701679c118e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2691792
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#854600}
--
wpt-commits: 05d7d56e799d33b5e75c640f5daf6a88f6225e9f
wpt-pr: 27630