Automatic update from web-platform-tests
view-transitions: Use default transform-origin for group elements
The spec text for computing the transform applied to
::view-transition-group elements is as follows:
"A transform that would map element’s border box from the snapshot root
origin to its current visual position."
This value needs to be relative to the center of the element's border
box. The current implementation computes the transform relative to the
element's top left corner with an additional UA style rule for
transform-origin to account for this. This is inconsistent with the UA
styles defined in the spec.
This change fixes the above by computing the transform relative to the
element's border bounding box center and removes the incorrect UA style
rule.
R=bokan@chromium.org, vmpstr@chromium.org
Fixed: 1420369
Change-Id: I0ee77266f29f880e8651111129e832b37eea5c48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4299931
Commit-Queue: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Auto-Submit: Khushal Sagar <khushalsagar@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112860}
--
wpt-commits: 6234499c6071b2343326842753cc94e24bf0b42b
wpt-pr: 38776
Automatic update from web-platform-tests
Reland "Implement CSSTransitionDiscrete which enables transitions on discrete properties."
Original patch: https://crrev.com/c/4219315
Revert: https://crrev.com/c/4305045
The original patch was causing bots to fail because they were somehow
making the tests marked as crashing fail instead of crash. I wasn't able
to reproduce the fail instead of crashing even with dchecks turned off,
but I am confident that relaxing the TestExpectations will make this
work again.
Bug: 1399631, 1413556
Change-Id: Id444255e727dbfed0fa61846d9d98653aa8eed67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4304846
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Auto-Submit: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112803}
--
wpt-commits: 9139057876d8d000767f9bc675bb3f2376861765
wpt-pr: 38803
Automatic update from web-platform-tests
Increase allowed fuzziness for perspective-transforms-equivalence.html.
This increases the fuzziness to match what is shown for Chrome on Linux
(which requires the larger maxDifference) and Edge on Windows (which
requires the larger totalPixels) on wpt.fyi, and hopefully fixes running
with wptrunner on our test platforms.
(I'm not entirely sure why this bug number is associated, but it's the
one tracked by wpt.fyi's data and in at least one tracking spreadsheet.)
See https://wpt.fyi/results/css/css-transforms/perspective-transforms-equivalence.html
Bug: 1076121
Change-Id: I012e3ff01a312078f0c7ffe0b0c86099afdb8bb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4305181
Auto-Submit: David Baron <dbaron@chromium.org>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112792}
--
wpt-commits: c00861eb3cb5c817dd7705c48803d12f81db2e68
wpt-pr: 38796
Automatic update from web-platform-tests
Revert "Reject Web Serial requests with an opaque origin"
Revert submission 4112689
Reason for revert: suspect for introducing test failures for
DedicatedWorkerTest.TopLevelFrameSecurityOrigin, for example
https://ci.chromium.org/ui/p/chromium/builders/ci/linux-ubsan-vptr/21391/overview
Reverted changes: /q/submissionid:4112689
Change-Id: I496ec21cc6a6e39dd3c2943b8fc7ce3d179a1f73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4307114
Owners-Override: Mikel Astiz <mastiz@google.com>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1112768}
--
wpt-commits: 3de4106d01456ddf3a8df9a03b99d6cb22d75abf
wpt-pr: 38805
Automatic update from web-platform-tests
Serialize variable-referencing properties as original text.
This uses more PartitionAlloc RAM (as much as 720 kB on the Video subtest),
but is more consistent with how custom properties are serialized.
We hope to gain some of that back later, by no longer storing the parsed
tokens. It also costs us a little in increased memory allocation costs
during parsing.
Parse (µs) Before After Perf 95% CI (BCa)
=================== ========= ========= ======= =================
ECommerce 1374 1384 -0.8% [ -1.7%, +0.3%]
Encyclopedia 7304 7341 -0.5% [ -0.9%, -0.2%]
Extension 1349 1362 -1.0% [ -2.2%, +0.1%]
News 8036 8116 -1.0% [ -1.4%, -0.6%]
Search 4999 5045 -0.9% [ -1.3%, -0.5%]
Social1 15309 15444 -0.9% [ -1.2%, -0.5%]
Social2 615 628 -2.1% [ -2.9%, -1.4%]
Sports 55919 56479 -1.0% [ -1.3%, -0.7%]
Video 36887 37470 -1.6% [ -1.9%, -1.3%]
Geometric mean -1.1% [ -1.5%, -0.7%]
Change-Id: I86d8f3b3d754974af2459de480a0ea7cc2107975
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4294946
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112736}
--
wpt-commits: 2715c7b13c1c2309bda8aa81dc1fda86ac239048
wpt-pr: 38769
Automatic update from web-platform-tests
Revert "Implement CSSTransitionDiscrete which enables transitions on discrete properties."
This reverts commit 367c58094d184ff90ef132789985bd4fc53c721a.
Reason for revert: Causing failures in blink-web-tests on many bots, for example: https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests/127213/overview
Original change's description:
> Implement CSSTransitionDiscrete which enables transitions on discrete properties.
>
> This feature enables transitioning discrete properties.
>
> This is based on the resolved CSSWG issue:
> - Transition discrete properties: https://github.com/w3c/csswg-drafts/issues/4441
>
> You can test display transitions with this CL on:
> https://output.jsbin.com/buquher/quiet
>
> Original patch: http://crrev.com/c/4182089
>
> Bug: 1399631, 1413556
> Change-Id: Icf5364b970233186794fa9faaa016e0e6542ec2b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4219315
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Joey Arhar <jarhar@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1112645}
Bug: 1399631, 1413556
Change-Id: I45cbf126b16402a88c7105d8204b342a79ded3d5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4305045
Commit-Queue: Adam Rice <ricea@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Adam Rice <ricea@google.com>
Cr-Commit-Position: refs/heads/main@{#1112668}
--
wpt-commits: ee989e5d26141612b5ecd4236ebad21a217449b6
wpt-pr: 38802
Automatic update from web-platform-tests
Implement CSSTransitionDiscrete which enables transitions on discrete properties.
This feature enables transitioning discrete properties.
This is based on the resolved CSSWG issue:
- Transition discrete properties: https://github.com/w3c/csswg-drafts/issues/4441
You can test display transitions with this CL on:
https://output.jsbin.com/buquher/quiet
Original patch: http://crrev.com/c/4182089
Bug: 1399631, 1413556
Change-Id: Icf5364b970233186794fa9faaa016e0e6542ec2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4219315
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112645}
--
wpt-commits: 005d050d16040db8bf64832d2d22e589e8c81b40
wpt-pr: 38399
Automatic update from web-platform-tests
[balance-text] Fix when `text-align` is not `left`
The `NGParagraphLineBreaker` adjusts the available width for
the `NGLineBreaker`, but the adjustments should not be visible
for `CreateLine` because it is used for aligning lines within
the original available width.
This patch restores the `line_opportunity` after the
`NGLineBreaker` is done.
Bug: 1251079
Change-Id: I83cdf1c120a6de0741180a27d7860ef8b70475cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4304620
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112644}
--
wpt-commits: ad172b15c6091ba467d23de9a5f84a58d173e429
wpt-pr: 38793
Automatic update from web-platform-tests
Break slow popover test into two pieces
This test got larger recently, and started timing out on CI bots.
This breaks the basic popover test into two pieces, in the hopes
that each is fast enough not to time out.
Bug: 1307772,1416284
Change-Id: I99b52fd245be9ecdf84896b74b0d63aca95a61ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4304905
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112623}
--
wpt-commits: 48994db2d529de64fc79623f7af54efa13166878
wpt-pr: 38800
Automatic update from web-platform-tests
[webtransport] Check existence of Origin header (#38782)
* [webtransport] Check existence of Origin header
The draft says clients must provide an Origin header [1].
[1] https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3-04#section-3.3
--
wpt-commits: 1393983442315fc6a96bacda5202036ca10327e3
wpt-pr: 38782
Automatic update from web-platform-tests
view-transitions: Fix test for max texture size.
The test in this patch is meant to test capture of an element which
exceeds max texture size. But the size used is not sufficient to hit
that limit on all platforms. The size doesn't even hit that limit in
WPTs without highdpi mode.
Fix the test to increase the size of the element such that it should
exceed max texture size on all platform/GPU configs.
R=bokan@chromium.org,vmpstr@chromium.org
Bug: 1409713
Change-Id: I1539f0afbe8b55df84a05caa68a615d69b8a4194
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4304220
Commit-Queue: David Bokan <bokan@chromium.org>
Auto-Submit: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112612}
--
wpt-commits: 9bd1828ce042198ff784f42d74a972866ba52c0d
wpt-pr: 38799
Automatic update from web-platform-tests
Reject Web Serial requests with an opaque origin
The Web Serial API tracks permissions using the origin of the top-level
document in the frame tree. If this document has an opaque origin then
there is no way to format the origin for display to the user in
permission prompts or to write their decision in the preferences file.
Access to the Web Serial API from such contexts should therefore be
blocked.
Bug: 1375133
Change-Id: I4552ae74d480aa8df9ff93527fc85618bc03b947
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4112689
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112561}
--
wpt-commits: fe0b80743ac716dcc9384a2aef7d8ad3549ab862
wpt-pr: 38152
Automatic update from web-platform-tests
web animations: Ensure replaceable have a valid effect target
The check for whether an animation is replaceable is currently limited
to whether it has an associated target element. In the case of
animations targeting pseudo-elements, the target is the originating
element. The animation also has an effect target which is the node being
animated and is the pseudo-element.
If the animation targets a pseudo-element which doesn't generate a box,
its effect target is nullptr since no node has been generated. This
also makes the animation not replaceable. Include a check for effect
target for replaceable animations to handle this case.
R=flackr@chromium.org
Fixed: 1419810
Change-Id: I45e4aaa4209b990ab19f2a540a322f1d7423ddb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4295760
Commit-Queue: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Auto-Submit: Khushal Sagar <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112517}
--
wpt-commits: fdc7e3f73f5360e1a6eda1bd316c39ae7b42e5e6
wpt-pr: 38749
Automatic update from web-platform-tests
Rename cross-site test case; use wildcard origin patterns
The "cross-origin" name was misleading, since the iframes in this test
case are also cross-site from the top-level doucment.
Change-Id: Iccdd48b44ba6793404d1245ec57748d0267ae356
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4303803
Commit-Queue: Shuran Huang <shuuran@chromium.org>
Commit-Queue: Chris Fredrickson <cfredric@chromium.org>
Auto-Submit: Chris Fredrickson <cfredric@chromium.org>
Reviewed-by: Shuran Huang <shuuran@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112450}
--
wpt-commits: e2f4f5fc7aa8c43bd92a12377388c4bab7aa686f
wpt-pr: 38794
Automatic update from web-platform-tests
Fix timeout failure for wpt select-event.html
WPT select-event.html test needs to wait for rendering in an
interopability manner before doing select event assertions.
The previous implementation of using 2 requestAnimationFrame()
causes Firefox test to be flaky as there wasn't a guarantee that
the rendering will be done before by then [1]. However, using
setTimeout(resolve, 0) breaks chrome as it doesn't guarantee
two frames are processed as chrome schedules through the next
animation frame. By having both, we should fix this flakiness
for all browsers.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1785615
Fixed: 1420110
Change-Id: Iaeaffbb04786b94b11daa3ed816d8679e0593d0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296974
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Di Zhang <dizhangg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112425}
--
wpt-commits: 4f242947b045f3fbb17d3b8114272bf8e2d8a18f
wpt-pr: 38745
Automatic update from web-platform-tests
[Reland] Use direct compositing for canvases rendered on the CPU
Before this CL, we already had the plumbing for presenting CPU-rendered canvases via GpuMemoryBuffer for direct compositing. That code path was originally implemented to support LowLatency mode. With this change, we exercise the GpuMemoryBuffer code path for "regular" latency canvases. This accelerates compositing, especially for pages that have many canvases.
With this change, MotionMark Images test runs significantly faster, especially with angle/metal enabled.
Reland of original cl: https://chromium-review.googlesource.com/c/chromium/src/+/4081383
The original cl was reverted because it break the overlay usage for devtools and the issue is fixed here.
Bug:1363627
Change-Id: I62583e43ff47f02281fe620f42897b77a99361e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296201
Commit-Queue: Yi Xu <yiyix@google.com>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112350}
--
wpt-commits: c580e7a20c40a6c4f44f1fb993969a673eab8e57
wpt-pr: 38781
Automatic update from web-platform-tests
Rewrite assertion with new semantics
The wpts are flaky. Although the failures are not yet re-produced on try
bots, see last comment of the associated bug, it's believed to be the
first-paint entry not showing up. It has been seen though very rarely on
local machines.
Previous the assertions are on number of entries. It is an indirect way
to verify that what entries should be retrieved with filter option of the
GetEntries() API. Also, the error msg is only about mismatch of
expected and actual numbers, which is not helpful.
This CL rewrites the assertions that verifies directly what entries
should be present and what entries should not. The first-paint is omitted because it is flaky. This is still correct because the test
semantic is that we should be able to get an entry from a same
origin subframe and should not be able to get any from a cross
origin subframe.
Bug: 1410530, 1420471
Change-Id: Iebe3b8d63f11d8ee8d02d2884fed16b4a52a57de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4289383
Commit-Queue: Hao Liu <haoliuk@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112339}
--
wpt-commits: ffdb61e5bdc7c2de2072d9d72f0fe8c738cb8287
wpt-pr: 38743
Automatic update from web-platform-tests
followup to #38653 for non-nightly node.js
--
wpt-commits: 919874f84ff3703365063e749161a34af38c3d2a
wpt-pr: 38791
Automatic update from web-platform-tests
Update Safari expectations for STP 164
The regression in STP 163 was fixed in STP 164, so flip this back.
--
wpt-commits: 4b4c1a75bfaa88ccfa52c51a042474ff33efd118
wpt-pr: 38789
Automatic update from web-platform-tests
[Private Network Access] Test redirect from same origin to cross origin
At [1], a concern was raised about the implementation that allows secure
same-origin private network requests without preflights. There was a
possibility that redirects were not correctly handled.
The above bug was fixed in [2], but it's still good to add some tests.
The test cases added in this CL test redirects from same-origin to
cross-origin or vice versa.
Failed tests in virtual/lna-allow-potentially-trustworthy-same-origin
are expected, because when
PrivateNetworkAccessAllowPotentiallyTrustworthySameOrigin is enabled.
This CL also removes the UUID from the response body because it prevents
UUID from going into the expected output.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/4221658/comment/ca7f33a7_1599ae6f/
[2] https://chromium-review.googlesource.com/c/chromium/src/+/4287225
Bug: 1382068
Change-Id: I96352dcba7c7c6517aac0108d24e1fa0491aacbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272862
Commit-Queue: Jonathan Hao <phao@chromium.org>
Reviewed-by: Titouan Rigoudy <titouan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112203}
--
wpt-commits: 505f1ff2ce0cfd4abbf6c96294cc3af2a6d27481
wpt-pr: 38615
Automatic update from web-platform-tests
use get_title() in ShellTestEnvironment.prototype.next_default_test_name
--
wpt-commits: 46e1750aa994319806887d7896d43f119ba05c7d
wpt-pr: 38653
Automatic update from web-platform-tests
[view-timeline]: Avoid reparse of keyframe rules containing timeline offsets
A full reparse of the keyframes is wasteful, when we just need to
re-sort. Previously, we had a bug where the effect invalidation caused
the composited animation to lag. This is because validateSnapshot
could trigger a second pass of layout update, but updateSnapshot could
not. We now avoid this problem entirely. Instead, we track if any
keyframe offsets are affected and simply clear the keyframe effect
cache if needed.
Injecting the neutral keyframes when processing the keyframe rules is
wasteful since already handled for property specific keyframes.
Removal of the neutral keyframes required updating getKeyframes to
return the expected results. Overall, the process seems cleaner now.
Added tests for keyframe retrieval as well as for interpolation at the keyframe boundaries.
Bug: 1408475
Change-Id: I18fc726c6f42e414760eb52dd8478c6930690238
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261369
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112198}
--
wpt-commits: c6b7fa7682f4ff3c5aa928443516473523234352
wpt-pr: 38625
Automatic update from web-platform-tests
Unflake loaf test
- loaf-buffered test: don't assume that the first LoAF entry is
the one we injected.
Bug: 1420756
Change-Id: Id9ba50d0b24b3cfa42c21f01fb45a5c808700352
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4302731
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112110}
--
wpt-commits: a84d334b31f3a59020be7ee164e504ab0c44f7e6
wpt-pr: 38783
Automatic update from web-platform-tests
Update WPT declarative shadow DOM polyfill
The polyfill wasn't updated when the behavior was changed in [1]. And
there were actually two competing polyfills, so this CL removes one
of them and points the rest to the survivor.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/4194055
Bug: 1379513
Change-Id: Ia95e08231aec0249b24dc3d251d4faeb02fab375
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4295761
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112066}
--
wpt-commits: ed273221b9cfcfd597f015fa42fb6274bc8b70e2
wpt-pr: 38750
Automatic update from web-platform-tests
Fix DCHECK in blink::BodyStreamBuffer::EndLoading
FetchDataLoaderAsFormData::OnStateChange() would call
DidFetchDataLoadFailed() on parse failure. It then would call it again
when it finished reading the input. The double call to
DidFetchDataLoadFailed() caused a DCHECK failure in
BodyStreamBuffer::EndLoading().
Fix it by stopping reading from the input after a parse failure,
ensuring that DidFetchDataLoadFailed() is only called once.
BUG=1412007
Change-Id: I38b7815020e85cbdedc38c207c945b1dee011083
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296718
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1112039}
--
wpt-commits: fb115d8f4a2955b8371b4b3b73a17f86ad752f25
wpt-pr: 38763
Automatic update from web-platform-tests
[MathML] Use 'safe' center positioning for display=block
Previously we'd just center the contents for `is_block_math`. Doing this
would lead to un-reachable content if the <math> element also had
overflow: scroll placed upon it.
Use 'safe' center positioning instead - that is center, but don't allow
the content to be place before the content edge.
Bug: 1416539
Change-Id: I367422c921d19a407e9457a0b4d4fbfe4dd55266
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4289160
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1112008}
--
wpt-commits: f8ee197c0e95774d8f586da3cb004f6e6d5ce2fe
wpt-pr: 38705
Automatic update from web-platform-tests
[BatteryStatus] Move most tests from wpt_internal to external/wpt
This CL moves most tests from wpt_internal to external/wpt to make
them become WPTs.
Bug: none
Change-Id: Idcc4799a1e08c5f4c4648242d95987db89b0e856
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274365
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Wei4 Wang <wei4.wang@intel.com>
Cr-Commit-Position: refs/heads/main@{#1111960}
--
wpt-commits: 3b791e5b10812a4ca4473d93679fc70d1a7f5f88
wpt-pr: 38603
Automatic update from web-platform-tests
[rsafor] Correct activation check in WPT
Passing is blocked on the outcome of crrev.com/c/4289832
Bug: 1414468
Change-Id: I989af6f11cbfd1e2fb9b3f9644f6041825dd9e2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4300150
Reviewed-by: Chris Fredrickson <cfredric@chromium.org>
Commit-Queue: Matt Reichhoff <mreichhoff@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1111761}
--
wpt-commits: 04b986a61c42a98619998e6efcb2e2f1f2f82239
wpt-pr: 38775
Automatic update from web-platform-tests
VT: Align to new proposed spec re ::view-transition sizing.
This patch removes pointer-events setting from UA stylesheets and
replaces ::view-transition styles with new proposed styles on
https://github.com/w3c/csswg-drafts/issues/8278#issuecomment-1449063571R=khushalsagar@chromium.org, bokan@chromium.org
Change-Id: I87404fcf42a4eb5c34f98f97cf678c26e65abf21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4294698
Reviewed-by: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1111635}
--
wpt-commits: f49456825338fef6f3828da0b663c3f28b88fa87
wpt-pr: 38760
