Automatic update from web-platform-tests
Remove feature flag if-statement in CSSMathExpressionNode::ToCalcValue
The value could be infinity and NaN from the function ToPixelsAndPercent().
But the value is conditionally clamped can create DCHECK failure somewhere if the feature flag 'CSSCalcInfinityAndNaN' is disabled.
Therefore, Remove the feature flag check statement for clamping.
Bug: 1248824
Change-Id: I3370a30815975d1935ccf6e583e6358e4fe2cf0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3216564
Reviewed-by: Mason Freed <masonf@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Seokho Song <0xdevssh@gmail.com>
Cr-Commit-Position: refs/heads/main@{#933860}
--
wpt-commits: 551712556fe03f60fc68628a7207ca60aca5dff2
wpt-pr: 31178
Automatic update from web-platform-tests
Tests for ::target-text.
These tests were written when ::target-text was implemented, but
changing window.location.hash for target text was not allowed at that
time, and did not allow for automated testing. Submit since that is now
possible.
target-text-004.html fails because currentColor for ::selection does not
fall back to using the text color from ::target-text.
Bug: 1136817, 1147859
Change-Id: Id512caec6ef7df8380f75fe82c79af27975991d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2521513
Reviewed-by: Manuel Rego <rego@igalia.com>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933854}
--
wpt-commits: d493ce131ffdedcea7f09d8c5055f7523b5b746b
wpt-pr: 31296
Automatic update from web-platform-tests
Find OOFs in the fragment tree when looking for a scroll anchor.
The HasOutOfFlowFragmentChild() bits are taken from
https://chromium-review.googlesource.com/c/chromium/src/+/2640403 by
obrufau@igalia.com, and the changes in ScrollAnchor is a counterproposal
to how that CL solves it.
In LayoutNG block fragmentation, OOF fragments are normally placed as
direct children of the fragmentainers, so that's where we need to look
for them.
Additionally, in cases where we're not inside block fragmentation, look
for OOF child fragments inside the fragment(s) generated by the
candidate. This is in preparation for the CL mentioned above (which will
no longer populate LayoutBlock's PositionedObjects when LayoutNG is
used).
OOFs are easily missed in ScrollAnchor::Examine(), because OOFs don't
contribute to layout overflow, and this is why we needed this extra
effort in the first place (crbug.com/692701).
This fixes wpt/css/css-scroll-anchoring/abspos-in-multicol-001.html
when LayoutNGBlockFragmentation is enabled.
Bug: 829028
Test: external/wpt/css/css-scroll-anchoring/abspos-in-multicol-001.html
Change-Id: I25bd7b3a56b2405ec76823993eefed4889361250
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3195930
Reviewed-by: Steve Kobes <skobes@chromium.org>
Reviewed-by: Oriol Brufau <obrufau@igalia.com>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933838}
--
wpt-commits: 39ef40f62d4f0ed55d2d9736140ec885ecce259e
wpt-pr: 31250
Automatic update from web-platform-tests
Support for font-style: auto and font-stretch: auto in @font-face
Support automatic variation range for the font-style and font-stretch
descriptors in @font-face rule. Added WPT tests static fonts and fonts
with 'slnt' and 'wdth' axis.
Bug: 973194
Change-Id: I1d671eb2423e02ff8cdc5017b2aa172fc113bcf3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3233039
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933832}
--
wpt-commits: 0e25815eb24f9a61cc1a9987378928e5538f70ac
wpt-pr: 31330
Automatic update from web-platform-tests
Add support for CORS non-wildcard request headers
- Add support for CORS non-wildcard request headers.
- Introduce a feature that controls the support.
- Introduce an enterprise policy that controls the support.
Bug: 1176753
Change-Id: I9f221a95e0958c0dcf924ae371c5e5323aee5be5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3226283
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933817}
--
wpt-commits: 19a3e93b3687042df5d288f9e2734afd55a40c7a
wpt-pr: 31286
Automatic update from web-platform-tests
Increase timeout in webmessaging/MessagePort_onmessage_start.any.js
This test was flaky on slower iOS debug similator configurations because of its short 100ms timeout. Bump the timeout to 1 second.
--
wpt-commits: 1fed135a400083e9e877245a983bef123bcfe514
wpt-pr: 31317
Automatic update from web-platform-tests
Use yaml.safe_load in canvas test generation
--
Teach html5lib test update to clone+install html5lib
--
Create a `wpt update-built` command
This allows removing some wrapper shell scripts, and means that
depandabot can manage updates of the requirements for updating built
tests. It also brings the UX in line with our other commands.
Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
--
wpt-commits: 15b688d61b46a7fed7aba3c9db9cc1e7de54328f, 38922310a7e15f912a1e1659b4a8e7a46ea31598, 3dd7c4df905ef743c2ec9d1ea939500d93c0ecaa
wpt-pr: 31243
Automatic update from web-platform-tests
Make WebBundle WPTs run against b2 bundles by default.
WPTs for WebBundle are currently using b1 bundles by default + some
tests use b2 bundles for limited coverage. This CL basically swaps the
two, making all WPTs to run against b2 bundles + basic test coverage for
b1 bundles.
Bug: 1249349
Change-Id: I9b5add2ffc35feb69da03395bd751436e681b879
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3233858
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Miras Myrzakerey <myrzakereyms@google.com>
Cr-Commit-Position: refs/heads/main@{#933789}
--
wpt-commits: 00f570328f8bb9185aeb2045d11c2305bec61236
wpt-pr: 31325
Automatic update from web-platform-tests
[FlexNG] Initial set-up for single-line column flex fragmentation
Spec: https://drafts.csswg.org/css-flexbox-1/#pagination
There are four different algorithms for fragmenting flex items
depending on the type of container. The first of which I will be
focusing on is fragmentation for a single-line column flex container
since it will be most similar to normal block fragmentation.
Because we need to know the item location before fragmenting, an
additional layout pass was added to NGFlexLayoutAlgorithm::
GiveLinesAndItemsFinalPositionAndSize() to take fragmentation into
account, at which point we know the final block offset of the item.
The looping mechanism in this method was replaced by a newly added
NGFlexItemIterator, which will iterate over items with break tokens
first, and continue from sibling items thereafter.
The code to set up the constraint space for item layout in
BuildSpaceForLayout() was updated with an additional call to
SetupSpaceBuilderForFragmentation() in the final fragmentation layout
pass.
Because we re-layout the entire flex container on every pass, and then
perform a final layout pass taking fragmentation into account, a new
bool was added to the constraint space's RareData to keep track of when
to avoid caching. We want to avoid caching the initial (non-fragmenting)
layout pass - this prevents the fragmented results from getting
overridden each time. There may be potential to avoid this if we can
store this information between fragmentainers, or if we cache it in a
new slot type instead of not caching at all.
With this CL, we can now support fragmentation for a single item in
a single-line column flex container that spans several fragmentainers.
In order to support multiple fragmented sibling items, additional work
will need to be done - including proper block offset calculation,
intrinsic block size calculation, and handling of a break before, all
of which have TODOs.
Some other interesting open questions and areas of investigation
include (TODOs included in the code for these, as well):
- How will the devtools logic work when items have multiple fragments?
- An additional layout pass is already made for items that stretch via
ApplyStretchAlignmentToChild(). It would be optimal if we could
make use of this layout pass to apply fragmentation, as well, to avoid
yet another layout pass in this case.
- How to handle flexbox writing mode roots? They are currently treated
as monolithic.
Bug: 660611
Change-Id: I35bcf407bbf741bb5df71f2acc70767be74090c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3212348
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#933725}
--
wpt-commits: e4b78613c5152a38fe6712643dcbe7582591427f
wpt-pr: 31168
Automatic update from web-platform-tests
Fix CompositeAfterPaint backface-visibility regression
Previously we set backface visibility to kVisible in the
TransformPaintPropertyNode for any css transform without explicit
backface-visibililty:hidden. This caused CompositeAfterPaint to
unnecessarily create composited layers for descendant transforms
of backface-visibility:hidden, and the composited layers had
incorrect backface visibility (which is crbug.com/1261095).
This CL lets TransformPaintPropertyNode for transforms that don't have
direct compositing reasons and backface-visibility-hidden inherit
parent backface-visibility to fix the regression.
Bug: 1260603
Change-Id: I5ad202b530ceaf20adb106bb7c626d3453c5bf1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3234662
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933716}
--
wpt-commits: efd81ed08a5f126111abfa870361637b0676f1b0
wpt-pr: 31334
Automatic update from web-platform-tests
Change effect phase calculation to be end inclusive for scroll animation
This fixes a problem where when scrolled all the way to the end of a
scroller, the animation would "finish" which meant the effect was no
longer applied, which is strange behavior for scroll based animations.
This adds an additional condition to the effect phase calculation that
allows it to account for whether or not it is at a timeline boundary
point.
I also added a few test cases related to phases and refactored the other
parts of the effect phase calculation to be more in line with the spec.
Bug: 1079300
Change-Id: I391df62da425b737500af6b66d83b596e7295e91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3176729
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Jordan Taylor <jortaylo@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#933672}
--
wpt-commits: b81a7a3db19b1ceb9c3a44da596abd9939f257a7
wpt-pr: 30918
Automatic update from web-platform-tests
Set pending update when there are previous interpolations for animations
In order to prevent transitions from starting when there's interference
from animations [1], we persist the previous animation interpolations
on CSSAnimations, and check that set when considering starting a
transition [2]. I assume checking the *current* interpolations is
not enough, for the case where an animation stops applying the same
frame a transition would be triggered.
This approach is questionable to begin with, but this CL will not
attempt to address that. This CL is about making sure that there is
no behavior change when enabling the CSSDelayedAnimationUpdates flag
(except within container query containers).
With CSSDelayedAnimationUpdates disabled, we will call CSSAnimations::
MaybeApplyPendingUpdate regardless of whether or not the update
we're applying is empty [3]. This will cause the previous-animation-
interpolations set to be cleared [4].
With CSSDelayedAnimationUpdates enabled, MaybeApplyPendingUpdate
will only be called if the update is non-empty, so the aforementioned
set is not cleared like it should be.
We do not want to *always* set a pending update, since there's some
overhead associated with this. However, we can address the issue by
setting a pending update whenever the previous-animation-
interpolations may need to be cleared.
[1] crrev.com/9e413848fb479438e79ad6a45ddc8704da07e7db
[2] CSSAnimations::CanCalculateTransitionUpdateForProperty
[3] Element::StyleForLayoutObject
[4] The start of CSSAnimations::MaybeApplyPendingUpdate
Bug: 1261155
Change-Id: I49db2c012fad7456276f077e98336dfc86935a6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3234546
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933637}
--
wpt-commits: b5054acd0933c8d6b9959f6f7d14e0b77ed4ee54
wpt-pr: 31332
Automatic update from web-platform-tests
[@layer] Add a WPT test for 'revert-layer' in transition
Bug: 1095765
Change-Id: I2119b003dd540bdbcdebde7abe57b907662f3057
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3235161
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933635}
--
wpt-commits: 13fe9a1057b874f10e780e008bc923d1fbd09736
wpt-pr: 31333
Automatic update from web-platform-tests
Fix element hash fallback in iframes
The text directive element-id fallback tries to scroll to the element-id
if a text match wasn't found. It does so in PerformPreRafActions since
element fragments cause focus which can execute script. Invoke(), where
the text fragment performs its text search, occurs from lifecycle
updates where script execution is forbidden.
Text directives used to be limited to main-frames but were enabled
explicitly for iframes in https://crrev.com/a71830a90b72f0a613fe9.
However, PerformPreRafActions wasn't updated to call into the
FragmentAnchor of an iframe
We also need to strip the fragment directives in
ElementFragmentAnchor::TryCreate. In cases where a text fragment is
successfully created, the element id fallback works by creating an
ElementFragmentAnchor from inside TextFragmentAnchor. However, if the
TextFragmentAnchor is blocked or not parsed correctly, the URL passed to
ElementFragmentAnchor in FragmentDirective::TryCreate will still include
the directives. A test for this was added in the new
same-document.tests.html
Bug: 1260135
Change-Id: Ib3f19b462016d34cc41d21b05933aa9cb822a9b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3224519
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933575}
--
wpt-commits: c8131af860cd65db70f7a5adc921f313db7aec5a
wpt-pr: 31259
Automatic update from web-platform-tests
Updated AnimationPlaybackEvent to return CSSNumberish for members
AnimationPlaybackEvent changed to use AnimationTimeDelta internally
and CSSNumberish externally.
Added support for scroll timelines.
Bug: 1251372
Change-Id: I2ff526dfc5d74a4b5917da2c64af29852aa9ecca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3222012
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Jordan Taylor <jortaylo@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#933567}
--
wpt-commits: 5f0a02b920a9183379260b5cd62b99fe4a148f37
wpt-pr: 31246
Automatic update from web-platform-tests
WPT: switch from HTML toward JS test. (#31312)
In the WPT repository for:
- COEP:credentialless
- Anonymous iframe
Switch from HTML toward JS test. Do it for every files, for consistency.
Bug: None
Change-Id: I099f43bc40aa7fbc2e462dcce701fe5ac4094453
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3211992
Reviewed-by: Antonio Sartori <antoniosartori@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933051}
Co-authored-by: Arthur Sonzogni <arthursonzogni@chromium.org>
--
wpt-commits: 426085a694201ae04729adc77065e46557a04bd8
wpt-pr: 31312
Automatic update from web-platform-tests
Test interactions of Fetch, ResourceTiming and ServiceWorkers (#31229)
--
wpt-commits: a52d48c168335cf67a1666408e5959beb531f880
wpt-pr: 31229
Automatic update from web-platform-tests
[SPC] Rename -tentative WPT test for SPC
SPC is no longer a tentative API (has a W3C spec, shipped in Chrome), so rename
the file to be clearer about the status.
Bug: 1241090
Change-Id: I6dd28f15e338328671899d252cbf6d749d0a9324
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3228796
Auto-Submit: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933446}
--
wpt-commits: 6c91acfef1e4c22de43b62a699aeb1dc10607685
wpt-pr: 31301
Automatic update from web-platform-tests
Update compositor keyframes on variable change.
This patch adds a check to see if any cached conversions were updated
during the process of applying animation updates. If so, we need to
update snapshots of composited keyframes. Previously, a change to a
non-animated variable that is referenced in a keyframe would not
trigger a snapshot update.
Bug: 1221622, 1245806
Change-Id: I9d90b3819ff1957f63625ff894aed079b455688e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3205715
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933445}
--
wpt-commits: 7ad2e85ea1061cc8403f9812869caceb224fde57
wpt-pr: 31127
Automatic update from web-platform-tests
Add tests for visibility event sequence in case of back/forward navigation (#31329)
* Add tests for visibility event sequence in case of back/forward navigation
* Remove whitespace
* nits
Co-authored-by: Noam Rosenthal <noamr@wix.com>
--
wpt-commits: 79e0eba39370fcd873fa04f76b952c08503395ea
wpt-pr: 31329
Automatic update from web-platform-tests
Introduce <script type=webbundle>
Introduce <script>-based API for subresource loading with Web Bundles.
See the design doc [1] for the motivation of switching from
<link>-based API to <script>-based API. The explainer [2] was already
updated to use <script>-based API.
This feature is guarded by `SubresourceWebBundles` flag.
We eventually drop the <link rel=webbundle> support and remove the
<link>-based API code once we can confirm <script>-based API can be
used as a replacement of <link>-based API.
This CL should be considered as the first step to switch to
<script>-based API. There are still gaps between <link>-based API and
<script>-based API, which will be addressed later [3].
This CL intentionally adds a very minimum test for <script>-based API
because there are already WPT tests for <script type=webbundle>. They
all have been marked as [ SKIP ] in TestExpectations until now. Now
some of them are passing after this CL.
We'll make the remaining tests pass in follow-up CLs, and also add
tests which are specific to <script>-based API as necessary. These
efforts should be tracked by crbug.com/1245166.
[1]: https://docs.google.com/document/d/1q_SodTcLuwya4cXt1gIRaVrkiaBfwWyPvkY1fqRKkgM/edit?usp=sharing&resourcekey=0-dqrFOGVCYsg8WRZ4RFgwuw
[2]: https://github.com/WICG/webpackage/blob/main/explainers/subresource-loading.md
[3]: https://github.com/WICG/webpackage/issues/670
Bug: 1245166
Change-Id: I5109b6e692baf10fd1d8a31a31d93176d4dc4ad2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128843
Commit-Queue: Hayato Ito <hayato@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933346}
--
wpt-commits: 47f30fc8a3227fb565186608e078451040de69c3
wpt-pr: 30816
Automatic update from web-platform-tests
Prerender: Upstream a test for cookies in same-origin prerendered pages
This CL upstreams a test for cookies in same-origin prerendered pages to
the WPT. The behavior of cookies is not defined in the spec yet, but we
already reached a consensus that the storage APIs including cookies in
same-origin prerendered pages are just allowed.
See the GitHub issue for details:
https://github.com/jeremyroman/alternate-loading-modes/issues/7#issuecomment-944358336
Bug: 1253158
Change-Id: I512a8e6b6f8a20f5464045900d67f8b2ef752266
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3232796
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933299}
--
wpt-commits: aea6e4f23f1cb516d5638f2444baf91be4397b17
wpt-pr: 31323
Automatic update from web-platform-tests
Integer interpolation should be rounded towards positive infinity.
Currently, interpolation of <integer> is rounding away from 0.
The interpolation's result should be rounded according to the spec,
https://drafts.csswg.org/css-values-4/#combine-integers, which is
"the result is converted to an <integer> by rounding
to the nearest integer, with values halfway between
adjacent integers rounded towards positive infinity."
Bug: 1257732
Change-Id: I0dc9db806b88e66bf326b848c4e4ac90ef868ed4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3225842
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Joonghun Park <pjh0718@gmail.com>
Cr-Commit-Position: refs/heads/main@{#933277}
--
wpt-commits: ac544dd30db7d2cc7ff6e6618c09b16470d5930f
wpt-pr: 31282
Automatic update from web-platform-tests
URL: test origin of blob: URLs
For https://github.com/whatwg/url/pull/655.
--
wpt-commits: 5acc42721ce5811462acc297bff75d33f999cd8f
wpt-pr: 31305
Automatic update from web-platform-tests
Need to propagate tallest unbreakable before forced breaks.
Even if there's a forced break inside the child added to the fragment
builder, we need to propagate the tallest unbreakable block-size, to get
column balancing right.
This fixes an existing test, but I felt that we needed a test that more
clearly illustrates this fix, so added that. The existing test still
fails in legacy layout, but for a different reason (layout is correct,
but outline painting order is wrong).
Took the opportunity to rename PropagateBreak() to PropagateBreakInfo(),
since this method doesn't only care about actual breaks. Also, no need
to call this one if no block fragmentation is involved.
Bug: 829028
Change-Id: Ie951817095267567b9fae578fd519b4ba76dc24c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3231178
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933116}
--
wpt-commits: 1a3a08970e5ff3beee45d552af463df6e40ba8e0
wpt-pr: 31313
Automatic update from web-platform-tests
[SelectMenu] Add basic support for form participation.
This CL adds basic form participation support by having
HTMLSelectMenuElement extend HTMLFormControlElementWithState that already
providies many behaviors (e.g. form association).
For now similar to <select>, name attribute is going to be required
for form participation and the value is going to be provided by
selectmenu.value.
Support for saving and restoring form control state and validation related
is going to be added in future CLs.
Bug: 1121840
Change-Id: Id9846a1fe9b781db5e4011fec77ff47faec2aaad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3224362
Commit-Queue: Ionel Popescu <iopopesc@microsoft.com>
Reviewed-by: Dan Clark <daniec@microsoft.com>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933001}
--
wpt-commits: 2e4e463c466f33a73131c4fe9fda80badf011e16
wpt-pr: 31253
Automatic update from web-platform-tests
content-visibility: Improve interactions with top layer.
When an element is added to top layer, and the content-visibility
ancestor prevents it from being drawn, then this patch ensures that the
element in the top layer does not get a layout object unless the
content-visibility lock is removed.
This is done as follows
- layout tree is detached when an element is added to top layer while
under a locked/skipped c-v subtree
- we don't store computed style (thus don't create layout objects) on
these top layer locked elements
- when removing the lock, we dirty either the path from the top layer
to the lock for style recalc or we cause the lock to do a full
descedant recalc if we can't dirty style.
R=futhark@chromium.org, masonf@chromium.org, ikilpatrick@chromium.org
Bug: 1251166
Change-Id: I93b4157ba3d67993175a93835c303faaa7f3d1c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3217939
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#933004}
--
wpt-commits: d63188269ad610bf9d25de368a6914f0bd1911eb
wpt-pr: 31209
Automatic update from web-platform-tests
Support for font-weight: auto in @font-face
Support automatic weight range for the @font-face header: font-weight:
auto range. Added WPT tests for variable and static fonts.
Bug: 973194
Change-Id: I4beb701e499df87652bd3b94d5ff3caed9dc27f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3189719
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/main@{#932987}
--
wpt-commits: e0b2f506efbe66afd35f730147e1ade766c871bf
wpt-pr: 31183
Automatic update from web-platform-tests
Update ua-clint-hints GREASE algorithm
The new implementation is behind a feature flag param.
After experimentation has confirmed safety, the old
implementation will be removed. A web platform test
is added to ensure the allowed characters are respected.
See the spec:
https://wicg.github.io/ua-client-hints/#create-arbitrary-brands-section
Bug: 1164423
Change-Id: I032f1c273d17e16d8f9adc921c9fc2fe508d4b9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3225903
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Aaron Tagliaboschi <aarontag@chromium.org>
Reviewed-by: Mike Taylor <miketaylr@chromium.org>
Commit-Queue: Matt Reichhoff <mreichhoff@chromium.org>
Cr-Commit-Position: refs/heads/main@{#932979}
--
wpt-commits: 20897f5d3a6ebe8a20fc26047aabe21034f1209a
wpt-pr: 31275
Automatic update from web-platform-tests
Clean up Client Hint WPT failures
The wpt.fyi test runner does not restart the browser on a failure like
the trybot runners do, so any state left by the tests makes for
flakiness.
Also, accept-ch-change.https.html *actually* wasn't working properly, in
that nothing was running except the initial check
Leaving the cache-related failures for a separate patch
Bug: 1257191
Change-Id: I6a51ad020a6dde748afa9fa1efeeaf4c1ccf8b0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3213006
Reviewed-by: Mike Taylor <miketaylr@chromium.org>
Commit-Queue: Aaron Tagliaboschi <aarontag@chromium.org>
Cr-Commit-Position: refs/heads/main@{#932969}
--
wpt-commits: 207e223d74fdc1f1103101d47105102fab667b4b
wpt-pr: 31298
