Automatic update from web-platform-tests
CSSDisplayAnimation: Transition none at beginning or end
This patch makes display animations function like visibility animations,
where animations to or from the invisible state are moved to either the
beginning or end in order to make the element visible during the entire
animation.
Bug: 1395394
Change-Id: Ifc8a657ddf612d32c730ff47b9eea92e8d1e5313
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4357115
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121380}
--
wpt-commits: 1c7c03b58d24fa64c4cd3240b8ce5bc6c4f62eb6
wpt-pr: 39095
Automatic update from web-platform-tests
Fix PST external web tests
Fix Private State Token external web tests that are behind in fetch
API updates.
Fixed: 1427210
Change-Id: If151beb5021840f83f585e6eaa66becd18c402c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4367498
Reviewed-by: Steven Valdez <svaldez@chromium.org>
Commit-Queue: Aykut Bulut <aykutb@google.com>
Cr-Commit-Position: refs/heads/main@{#1121342}
--
wpt-commits: 08d8520cd3d088eb83640dfc478081c565ef81e2
wpt-pr: 39169
Automatic update from web-platform-tests
[FLEDGE] Add WPT tests where script requests receive no response.
The socket is just closed without sending any data. This is probably
the best we can do to simulate network errors.
Bug: 1425952
Change-Id: I32472c27c922a261422489b4e0107cf77c999761
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4362155
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121328}
--
wpt-commits: e8e184f5bb049891c87f4b97556cdd40e7a7be9c
wpt-pr: 39166
Automatic update from web-platform-tests
Add SoftNavigations/TaskAttribution support for ViewTransitions
ViewTransitions have a callback that didn't have its parent task ID
properly set, as part of TaskAttribution.
This CL fixes that, and ensures they are properly tracked. (and hence,
that SoftNavigationHeuristics properly work with ViewTransitions)
Change-Id: Ia531017fb9e86efde93b2307f2e4a2d8e7c994ce
Bug: 1405448
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4350628
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Scott Haseley <shaseley@chromium.org>
Reviewed-by: Khushal Sagar <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121132}
--
wpt-commits: a3609cbb1b4aba56d794058a55cf44a8f56d8824
wpt-pr: 39080
Automatic update from web-platform-tests
[css-color-5] add extra tests for color-mix() with the transparent keyword (#39139)
--
wpt-commits: ff0503efa666e66c0b55b3f3b2fb1b24afd709fb
wpt-pr: 39139
Automatic update from web-platform-tests
Reland "[anchor-position] Make `anchor` attribute work for non-popovers" (#39114)
This reverts commit 80faa9503f457b4a09fa31912eafc7eefd585568.
Reason for reland: Performance regression fixed. See diff with PS#1.
The original patch used an expensive condition to decide whether to
install an AnchorElementObserver, which caused performance issues. This
patch changed to installing observer only when the `anchor` attribute
(IDL or content) is modified.
Original change's description:
> Revert "[anchor-position] Make `anchor` attribute work for non-popovers"
>
> This reverts commit 4abd0d04120561b80ad2e6dd398651d7e909463f.
>
> Reason for revert: Caused a lot of performance regressions.
>
> Original change's description:
> > [anchor-position] Make `anchor` attribute work for non-popovers
> >
> > This patch reimplements how we mark elements that are implicit anchors.
> > Previously it was only marked for popover element's implicit anchors,
> > and now it works for all implicit anchors. This is done by a new class
> > AnchorElementObserver that observes all possible changes in implicit
> > anchor and replaces the old PopoverAnchorObserver.
> >
> > This patch also reveals two existing issues:
> > 1. Element::GetElementAttribute() may return non-null result even if
> > the element is out of tree scope. As fixing the bug is out of the
> > scope here, this patch just works around it. crbug.com/1425215 was
> > filed.
> > 2. popover-anchor-idl-property.html has some bugs that made it pass
> > previously. This patch fixes those bugs.
> >
> >
> > Fixed: 1417346
> > Change-Id: I798977ab1ed7df0c528b7eb98c64fc04476e6106
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4338487
> > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> > Reviewed-by: Mason Freed <masonf@chromium.org>
> > Cr-Commit-Position: refs/heads/main@{#1118933}
>
> Bug: 1425610, 1425635, 1425650
> Change-Id: I50a650f011e097c48c0efd110cf765d0df5835e4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4353985
> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
> Reviewed-by: Mason Freed <masonf@chromium.org>
> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1119483}
Bug: 1425610, 1425635, 1425650
Change-Id: I222e0cc302e16f208314641b153ce1746ca814a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4355591
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121203}
Co-authored-by: Xiaocheng Hu <xiaochengh@chromium.org>
--
wpt-commits: fd7ffa75cd387869b077c3b3eff233ada9075a97
wpt-pr: 39114
Automatic update from web-platform-tests
view-transitions: Clip snapshots to max texture size/viewport. (#38946)
If an element's painting exceeds viewport bounds, clip it down to max
texture size or twice the viewport bounds by painting the subset which
is closest to the snapshot root.
This involves the following 2 changes:
1) A new ClipNode is introduced to paint the desired subrect when
rendering this element in paint, raster and compositing. All these
stages should render only this subset.
2) The object-view-box on the replaced element is still set to the
ink overflow rect. So at paint time, we adjust the replaced content
rect to the actual subset that will be painted based on the clipping
above.
R=pdr@chromium.org, vmpstr@chromium.org, bokan@chromium.org
Bug: 1409713
Change-Id: If81bc67ad6ffe49d68e4470a6717b704edafcd3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4330193
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Auto-Submit: Khushal Sagar <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121126}
Co-authored-by: Khushal Sagar <khushalsagar@chromium.org>
--
wpt-commits: 87e344fb91b3f675b5748bfb64e14bdfd4df8169
wpt-pr: 38946
Automatic update from web-platform-tests
[motion-1] Make <ray-size> of ray() function optional
As per spec change <ray-size> is now optional,
defaulting to <closest-side>.
Spec: https://drafts.fxtf.org/motion/#valdef-ray-ray-size
Change-Id: I739ead2552528b5fdb755a2b1ab13bc4c4510b5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4360295
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Daniil Sakhapov <sakhapov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121144}
--
wpt-commits: f36421b353943727fd56702eb0767855c4656174
wpt-pr: 39140
Automatic update from web-platform-tests
Fix MicrotaskCheckpoint completion steps
Previously the promise resolution steps would only happen when
Agent::PerformMicrotaskCheckpoint was called. This was incorrect because
there were other microtask checkpoints that either call into the
EventLoop directly or use a v8::MicrotaskScope block to run tasks.
Ensure all calls to running a microtask checkpoint end up calling to the
Agent::RejectPromises callback. This code is behind an enabled feature
flag for safety.
Bug: 1027230
Change-Id: I557e9ad092eed51e8e1ae20b589f71f5ddc27b5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4355716
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Scott Haseley <shaseley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1121123}
--
wpt-commits: 4887e6d074c6bcf83fc00ae5536157c236eea365
wpt-pr: 39124
Automatic update from web-platform-tests
WebKitGTK: run the tests in the CI (TaskCluster) with 4 parallel jobs (#38723)
WebKitGTK tests have started to timeout on the CI again. The issue is caused
because there is a 2-3 hour maximum time allowed for each test chunk
to run and we are hitting the time limit.
In the past we tried to fix this by raisin this timeout or the number of chunks
See commits: ac16b46831 and 6f7c2fd96f and a218d10eb9
This time instead of rising the time limit or the number of chunks let's try
to run the tests in parallel. Using 4 jobs gives 4x speed-up even on a machine
that only has 1 core because we avoid waiting serially for tests that are
slow or timeout. For more details see:
https://github.com/web-platform-tests/wpt/issues/38723#issuecomment-1470938179
--
wpt-commits: e66b3f69f6172d2f5c9320eb390211c2d3dc9ad5
wpt-pr: 39021
Automatic update from web-platform-tests
Clear <selectmenu> selection when setting invalid value via JavaScript
This CL clears the <selectmenu>'s selection when the <selectmenu>'s
value is changed to an invalid value. This brings <selectmenu>'s
behaviour inline with <select>'s behaviour.
BUG=1426875
TEST=selectmenu-value-selectedOption.tentative.html
Change-Id: Idb22f47e97152cb2320d78fde786b898aaf294a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4362638
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1120919}
--
wpt-commits: 50a5308a2a009b991c0fa9a339127a71f2ad3f56
wpt-pr: 39146
Automatic update from web-platform-tests
CSSTransitionDiscrete: Replace transitions/unanimatable-properties.html
unanimatable-properties.html tests that a few properties aren't
animatable, but CSSTransitionDiscrete aims to make those animatable so
this test is invalid.
There is one property in this test which should remain unanimatable:
transition-duration. In order to account for this, I've created a new
WPT which tests that transition-duration, transition-delay, and
transition-property are still not animatable.
Bug: 1399631, 1413556
Change-Id: I091d358796559951436c7d63a181646af09472f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4349871
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1120916}
--
wpt-commits: 816ba285e367da463825811d21708c74b0cfdc93
wpt-pr: 39126
Automatic update from web-platform-tests
Ensure navigateerror doesn't fire without navigate when a traversal is preempted.
This allows us to assert that NavigationApi::AbortOngoingNavigation()
is only called when ongoing_navigate_event_ is non-null.
This requires a slight reordering of the early-exit cases in
NavigationApi::DispatchNavigateEvent(), but guarantees that ongoing_navigation_ only gets set non-null if a navigate event will
definitely fire.
Change-Id: If1213c9fd2500adf99427ea5115733f99ad49ea2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4355034
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Auto-Submit: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1120859}
--
wpt-commits: 5f365dcd5407bebc5830496cbd679afca81afc20
wpt-pr: 39093
Automatic update from web-platform-tests
Add tentative shadow dom selection related tests written by @rniwa (#39144)
--
wpt-commits: 55dd5fe143e41101ad9ad19e6171c2468dc960d2
wpt-pr: 39144
Automatic update from web-platform-tests
view-transitions: Dont use view-transition-name in ref.
If the property has an undesired side-effect, the test would still pass
since the ref also uses the property. Remove it so such failures are
detected.
R=vmpstr@chromium.org
Change-Id: Ia734294440ac99cb5ea42f358bbcfb196831009a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4361541
Commit-Queue: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Auto-Submit: Khushal Sagar <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1120704}
--
wpt-commits: b0ae2d8db4210ab4e55a35a9567cc07d36e4c5fc
wpt-pr: 39145
Automatic update from web-platform-tests
VT: Handle fragmented shared elements.
This patch skips adding fragmented elements into the shared element
set. If an element becomes fragmented during the transition, then the
transition is skipped.
R=khushalsagar@chromium.org
Fixed: 1424806
Change-Id: I3e3a7305a75c16b06a53c891954a0961dcb2eedf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4357275
Reviewed-by: Khushal Sagar <khushalsagar@chromium.org>
Commit-Queue: Khushal Sagar <khushalsagar@chromium.org>
Auto-Submit: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1120701}
--
wpt-commits: c40f65bd1be65620bc489fff98d98ef69eb7d540
wpt-pr: 39099
Automatic update from web-platform-tests
Fetch: additional blob: URL range request tests
As well as a fix for one of them.
For https://github.com/whatwg/fetch/pull/1621.
--
add some more tests, also properly use async
--
wpt-commits: a1b791a44a4e22300ea511cf66351477c6565aa7, 8cad07b60d4241934644aeb4e0f95dc6c3a44f04
wpt-pr: 39108
Automatic update from web-platform-tests
WebCryptoAPI: refactor small order tests (#39053)
--
wpt-commits: 188993d46b95c9c0414ba2cef8751f5e19d3d498
wpt-pr: 39053
moz-wptsync-bot
Joey Arhar
Aykut Bulut
Matt Menke
Ana SollanoKim
Shuran Huang
Romain Menke
Yoav Weiss
Blink WPT Bot
David Bokan
Daniil Sakhapov
Dave Tapuska
Carlos Alberto Lopez Perez
Sam Sneddon
dependabot[bot]
Yuzu Saijo
Peter Kotwicz
Nate Chapin
Adithya Srinivasan
Sean Feng
Khushal Sagar
Vladimir Levin
Vitor Roriz
Anne van Kesteren
Filip Skokan