Automatic update from web-platform-tests
[CSSTransitionDiscrete] Fix custom property issues
When attempting to transition a custom property with universal syntax,
we hit a DCHECK in StyleBuilder::ApplyProperty because we send
a CSSVariableReferenceValue, which is normally expected to be resolved
at this point. However, such custom properties represent their
computed values as CSSVariableReferenceValues, and the discrete
transitions machinery sends those computed values to ApplyProperty
without "transformations". This is expected behavior as of CL:4315803.
Representing the computed value of universal custom properties with
CSSVariableReferenceValue is a bit suspicious and might warrant further
investigation, but this CL does not attempt to address that. Instead
we alter the DCHECK to expect CSSVariableReferenceValues for relevant
custom properties.
Also:
- Fixed usage of irrelevant custom property in the WPT
token-stream-type-type-interpolation.html.
- Fixed accumulation of "transitionrun" event listeners when
testing multiple transitions in the same .html file
(e.g. custom-property-transition-mismatched-list.html).
WPTs related to <transform-function> and <transform-list> are still
failing, because we don't implement interpolation for those syntaxes
yet.
Bug: 1399631
Change-Id: I22f0766921061216421839def84bc305edda2a41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4334509
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118779}
--
wpt-commits: e6c2d4cacfa621bc2656b577c1fb63f080bac2f5
wpt-pr: 39051
Automatic update from web-platform-tests
Test which XSLT functions are defined
This currently expects only functions defined in XSLT 1.0 (and references) to be defined. This matches what all browsers currently implement.
--
wpt-commits: d963cd40e87f20bbfaaffdb9eca2e539bac4d631
wpt-pr: 39057
Automatic update from web-platform-tests
CSSTransitionDiscrete: Fix counter related crashes
The generated code in CounterIncrement::ApplyValue expects to receive a
CSSValueList with a CSSValuePair inside of it, so this patch adds a
CSSValuePair to ComputedStyleUtils::ValueForCounterDirectives
Bug: 1399631, 1413556
Change-Id: If38d51d026965b2f481a9ed6432ce519587847ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4310132
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118697}
--
wpt-commits: 98afc8a86461237414d32da9e6628499c0a0022a
wpt-pr: 38817
Automatic update from web-platform-tests
Fix#8122: Upstream Mozilla counter-style tests
These don't cover all of the counter styles, but they give us automated tests
for most of them.
They are all originally authored by @dbaron and @upsuper.
--
wpt-commits: 5e9421703a3de453d0792109a714f624e5185f27
wpt-pr: 8150
Automatic update from web-platform-tests
Collect popover invokers on root instead of document
See this HTML spec PR:
https://github.com/whatwg/html/pull/8993
It points out that it would be better to look within `root`
rather than `document` for invokers. Otherwise this use case
will be broken:
<div>
<template shadowrootmode=open>
<button popovertarget=p1>Click</button>
<div popover id=p1>Popover 1
<button popovertarget=p2>Click</button>
</div>
<div popover id=p2>Popover 2 (I'm not detected as a being related to p1)</div>
</template>
</div>
I.e. nested popovers entirely within a shadow tree. This CL
fixes that behavior and adds a test.
Bug: 1307772
Change-Id: I28521ec1008d43994ca738c5673da3b704d7ba9c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4335444
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118671}
--
wpt-commits: 887ed601ff82d1cee8a358559e2c963528e6520b
wpt-pr: 38981
Automatic update from web-platform-tests
Fix inconsistent hasStorageAccess behavior for A(B(A)) frame tree case
This change for document.hasStorageAccess() is based on spec PR
fd28dc0543.
Bug: 1422628
Change-Id: I72cc1bb21a5d075a00b4b6719e2010855e5c2a63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4340989
Reviewed-by: Johann Hofmann <johannhof@chromium.org>
Commit-Queue: Shuran Huang <shuuran@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118658}
--
wpt-commits: 186820b4ea00e96be00a7f57a2f709c67d78d05c
wpt-pr: 39019
Automatic update from web-platform-tests
Use base::ValuesEquivalent for custom property style queries
We previously compared the tokens from the tokenizated string instead.
Add tests for matching and serializing original string in style()
queries.
Bug: 1302630
Change-Id: I2768b930407f65c979b320597276e0d5d01a1b93
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4342894
Reviewed-by: Steinar H Gunderson <sesse@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118626}
--
wpt-commits: 0b9590a78d353217ae0bc6321ecc456f2da197ec
wpt-pr: 39052
Automatic update from web-platform-tests
Initial implementation of the X25519 algorithm
This CL implements the DeriveBits and import/export operations
for the X25519 algorithms (spki, pkcs, raw and jwk).
Additionally, it adds the new algorithm in the registry and implements
its normalization, which is quite simple due to the lack of parameters.
The feature is implemented behind the WebCryptoCurve25519 runtime flag
for now. See the intent-to-prototype request [1] for details.
[1] https://groups.google.com/a/chromium.org/g/blink-dev/c/n0uKIqfypW0/m/xu5UBbaBAwAJ
Bug: 1370697
Change-Id: Ibad2a728a5b25b40c130e4da270747104ae056ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4016576
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1118402}
--
wpt-commits: 1406b5c0d07b5e8dd08e328c451e42c23f3b96c8
wpt-pr: 37063
Automatic update from web-platform-tests
Split vr_services.mojom to multiple files based on its functionality.
Method moved from vr_service to xr_session:
enum XRSessionFeature()
enum XRSessionMode()
Bug:1420093
Change-Id: Ide102ec4495d32aca6aedc5f2233b2ed6a101058
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4307278
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Brendon Tiszka <tiszka@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118389}
--
wpt-commits: 4904eff5021a5ab057de49fbbf0b4916b5a1f336
wpt-pr: 38962
Automatic update from web-platform-tests
InlineLayout: add parsing logic for the text-box-trim property
This CL includes:
- Introducing the new property.
- Adding a new RuntimeEnabledFeature
- Adding the parsing logic
- Adding initial web tests for parsing
Bug: 1411581
Change-Id: I8e9f6f023a505ac1ae97a827048d836972e97a73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4296655
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118311}
--
wpt-commits: 1eb5a3613d962922f982715e3ca09d4aedbb6a35
wpt-pr: 38762
Automatic update from web-platform-tests
[wptrunner] Downgrade URL validation in content shell driver (#39036)
See the comment in `testharnessreport-content-shell.js`. URL mismatches
will no longer be treated as a harness `ERROR`.
For the URLs to match as much as possible, this change partially undoes
web-platform-tests/wpt#39007, which broke validation for final URLs with
fragments. Instead, we use the standard `URL(...)` instead of `<a>` to
parse the original `location.href`.
--
wpt-commits: 071134cb4d44b95f8068828830498a19c60ad120
wpt-pr: 39036
Automatic update from web-platform-tests
Scheduling APIs: Implement scheduler.yield() prototype (part 1)
This adds the full API surface of scheduler.yield() to the IDL and
implements all the options except inheritance (split off to keep the
size reasonable). Details:
- The scheduler's fixed and dynamic priority collections are
mirrored for continuations, and algorithms have been updated to
select the collection based on WebSchedulingQueueType.
- When yield is called, the options are used to get a TaskSignal
for the continuation, using the same algorithm as postTask().
This in turn is used to select the continuation queue which is
used to schedule a DOMTaskContinuation (wrapper around resolving
the yield() promise).
- Passing "inherit" for the signal or priority option will CHECK.
This will be implemented in a follow-up CL.
- Tentative WPT test coverage is added for the implemented portion
of the API.
Bug: 979020
Change-Id: I601cd0ce801f02bdc236995124a36951431da5b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4324266
Reviewed-by: Nate Chapin <japhet@chromium.org>
Commit-Queue: Scott Haseley <shaseley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118256}
--
wpt-commits: 8ab8d9d6ae09d7cf62657115a1fd4366b7de8b11
wpt-pr: 39001
Automatic update from web-platform-tests
Only add trailing border/padding to the right fragment.
We used to always subtract trailing border/padding for every fragment
that shouldn't have it, but this changed for table cells in CL:4303193.
To fix this, make sure that we only include trailing border/padding when
at the fragment that has the block-end edge of the box.
Bug: 1425075
Change-Id: Id7afa2eee764e1a8bb3017a90b212495278fe623
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4345873
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118245}
--
wpt-commits: e385e89cfcfb7170f098736c8ecefa89451aa62a
wpt-pr: 39035
Automatic update from web-platform-tests
Add test coverage for VP9 simulcast in WPTs.
The majority of this work already happened inside third_party/webrtc (webrtc:14884). This CL simply adds test coverage for VP9 simulcast,
with and without using scalabilityMode.
For now, a field trial is needed in order for the scalabilityMode path
to opt-in and pass the test.
Bug: webrtc:14884
Change-Id: I453e15f329f424b74c6f82befe718c237dc9bff1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4340569
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Ilya Nikolaevskiy <ilnik@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118156}
--
wpt-commits: d70009880ec0c8cff26adf08f56cd44945cde35d
wpt-pr: 39027
Automatic update from web-platform-tests
[css-color] unwrap lab/oklab and lch/oklch for-loops (#39029)
Make separate tests for lab() vs. oklab() and lch() vs. oklch(), since with clamping of L > 100% they will have different computed values (#39000).
--
wpt-commits: 490fc650dac1e61fd2be2dc76ce571a9a89e0135
wpt-pr: 39029
Automatic update from web-platform-tests
[rsafor] Rename requestStorageAccessForOrigin to requestStorageAccessFor
This allows for evolution of the scope of the permission without
requiring deprecation of the old name.
Change-Id: Iee11f56a41ec116b800515adaf4ee3fe7fc91e26
Bug: 1424452
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4337982
Reviewed-by: Dominic Farolino <dom@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Matt Reichhoff <mreichhoff@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1118038}
--
wpt-commits: b185124819558842359d60f2715797ceaf997fa6
wpt-pr: 38996
Automatic update from web-platform-tests
webcodecs: Support for per-frame QP configuration in VideoEncoder
This is a resubmit of https://crrev.com/1117235
Currently only software AV1 and VP9 are supported.
- IDL changes necessary pluming
- web tests and
- improved error messaging for profiles and config params
Demo: https://webcodecs-qp.glitch.me/
Bug: 1424154, 1406372
Change-Id: Ia7a89364700184fcfe55d0b6b298785784f1332d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4342072
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1117801}
--
wpt-commits: eb59e8b777bb8d80932cc241a6a417c69a891c15
wpt-pr: 39018
Automatic update from web-platform-tests
Improved calc-serialization-002.html according to comments in Issue 3741
--
Updated number of sub-tests
--
Tweaked the calc(4vmin + 0pt) sub-test accordingly
--
wpt-commits: 436fce53d453a3701a92deed9bfbb538918452b4, c39e882f945f64e10b4c678c3ceeb5ce366d366d, 7057faf126ad4385522f0ce76eb3f5b816dca750
wpt-pr: 38245
Automatic update from web-platform-tests
[view-timeline] Support timeline offsets in programmatic keyframes
This patch adds parsing for timeline offsets in programmatic
keyframes. The loose ordering and bounds checks have been relaxed
to only apply to explicit keyframe offsets. This is achieved by
deferring resolution of timeline offsets until after the range and ordering checks.
Migrated a non-WPT test to WPT for keyframe exceptions. The wording
of the exception is not specified; however, the fact that an
exception must be thrown for loose ordering or range violation is
explicit in the spec.
getKeyframes tests for a programmatic animation are intentionally
being deferred to a followup CL, once we have explicit timeline
offsets in the set of reported keyframes.
Bug: 1383158
Change-Id: Id323ea2474d88765e163d45e27632857d1b3d3e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4307939
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1117565}
--
wpt-commits: f791e89cb111b15467d28ef4d9d436af7bc004a3
wpt-pr: 38831
Automatic update from web-platform-tests
[wptrunner] Fix test ID reported in `testharnessreport-content-shell.js` (#39007)
--
wpt-commits: f80ae3f8af807fa33c335ea5626225a34ed11520
wpt-pr: 39007