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
Automatic update from web-platform-tests
Update script result_ownership tests to check that handle id is only set on root
--
wpt-commits: 4662f28713fed8071e0a670190805206c4fde7f7
wpt-pr: 35966
Automatic update from web-platform-tests
[FlexNG] Don't clamp flex row-gaps when fragmenting
We don't clamp flex item margins when an item breaks before to more
accurately handle alignment. Thus, we should similarly do the same
for row gaps. Currently, we will clamp row gaps (or at least part
of row gaps - there were other bugs uncovered while investigating),
so this CL updates the logic to correctly preserve the row gap,
matching Firefox's behavior.
To accomplish this, we needed to adjust item offsets based on various
cases, but we only want to make this adjustment the first time the
row breaks before. Thus, the break before row tracking in
NGFlexBreakTokenData was updated to an enum of three values to keep
track of whether the break token represents a break before a row,
as well as whether or not it is the first time we have broken
before that row.
Additionally, when we perform the logic to determine if a row should
break before, we needed to update the call site to pass in the adjusted
row offset to ensure we are handling breaks correctly.
Bug: 1413089
Change-Id: Ieb9cc4470cd96146cddf4f330aefdd06af1a1626
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4335769
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1117559}
--
wpt-commits: 2c5ee97e98669eac9d887421b67d0ff0b451a1ed
wpt-pr: 38969
Automatic update from web-platform-tests
Improve popover-attribute-all-elements.html (#39009)
Improve testing for elements that don't render.
--
wpt-commits: 6189b0755e8c10cc27b0254a5afce38421035db2
wpt-pr: 39009
Automatic update from web-platform-tests
[ComputePressure] Fix focus related WPTs
This CL resolves two issues:
1. Missing function call "observer.observe('cpu')".
2. iframe.contentWindow.focus() does not work before the iframe is
loaded.
Bug: none
Change-Id: Ife7fce64120048e5bcdf40242d1e80fc048b78cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4335229
Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Wei4 Wang <wei4.wang@intel.com>
Reviewed-by: Fr <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/main@{#1117303}
--
wpt-commits: 77f6cca6d9f2bb60c1da476e7a5bb4f9ee3a6cd7
wpt-pr: 38977
Automatic update from web-platform-tests
Reland "Make input element UA shadow tree creation lazy"
This is a reland of commit 259286fb5706438088c858361ff942239598ea3b
Diff:
third_party/blink/renderer/core/html/forms/text_field_input_type.cc::UpdatePlaceholderText
If the placeholder is not null, we should ensure the shadow subtree has been constructed and update the placeholder text instead of just return here if the shadow subtree is not built.
Original change's description:
> Make input element UA shadow tree creation lazy
>
> This CL comes from WebCore https://trac.webkit.org/changeset/290639/webkit,
> it claims 0.5% progression on Speedometer2, the chromium pinpoint result
> shows a 0.6% progression on Speedometer2.
>
> This CL lazy create shadow subtree until one of the following happens:
> 1. the element is inserted into the document
> 2. the type="" or value="" attributes are changed before the element is inserted into the document
> 3. any DOM methods that need access to the InnerEditorElement() are called on the element before the element is inserted into the document
>
>
> Change-Id: I5fd6743182d65be7e00fcb59480a5b28af289b76
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4111088
> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1110526}
Change-Id: Ie6657cce1e1edc381b494709af25f2a2243b9714
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4330348
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1117160}
--
wpt-commits: 597c96814cb435d6f50f87193d368fc1595bc303
wpt-pr: 38971
Automatic update from web-platform-tests
Fix html/semantics/embedded-content/the-video-element/intrinsic_sizes.htm
Reading .width/.height on the computed style returns the used value, and
thus it will flush any pending layout changes. This means that the
assertions that attempted to assert the "before" state were incorrect.
Remove them.
Bug: 1234202
Change-Id: Ib24d65ecf353d3cb3acf50e4c0d35ee729d827df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4337505
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1117103}
--
wpt-commits: 444a206a4f1bbf7de78af68c5cc6f21b564ddcde
wpt-pr: 38995
Automatic update from web-platform-tests
[@scope] Enable implicit :scope and relative selectors for <scope-end>
By simply propagating the 'in_nested_style_rule' flag, we enable
the two features:
- Implicitly prepending a :scope compound with a descendant
combinator if the selector is not :scope-containing.
- Relative selectors.
Bug: 1280240
Change-Id: I117378791b0034be3d2f168d067712acf744e3c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4291114
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1117080}
--
wpt-commits: 7c083dd76a0a8d9eb1e5a320fa6a2335d058ce34
wpt-pr: 38990
Automatic update from web-platform-tests
Fix Clear-Site-Data WPT that clears active service worker.
A service worker was handling the network request for an iframe page
load. That load also cleared storage (and service workers) via Clear-
Site-Data. This interrupted the page load and prevented the test from
completing.
Specifically, 'support/echo-clear-site-data.py' was returning
[Clear-Site-Data: "storage"] which clobbered the service worker which
was registered for 'support/' which prevented the subload of
'support/test_utils.sub.js'.
The solution is to narrow the scope of the service worker so that it
doesn't apply to the page the iframe is loading.
Bug: 1198698
Change-Id: I6724f5ef8e2140d031b6c570b9c708359a97d140
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4334942
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1116968}
--
wpt-commits: 2dc57a5fe3cfc69232cb281b882e265ba1fcb39c
wpt-pr: 38966
Automatic update from web-platform-tests
[@scope] Make '&' in <scope-end> resolve to <scope-start>
Instead of storing the <scope-start> (i.e. From()) as a CSSSelectorList,
store an empty StyleRule with that same list of selectors.
This allows us to pretend that <scope-start> is the ancestor rule
for nesting purposes when matching <scope-end>, as required by spec.
The nesting selector (&) needs to work other places too, but that is
for future CLs to handle.
https://drafts.csswg.org/css-nesting-1/#nesting-at-scope
Bug: 1280240
Change-Id: I52bed7537a6892746bbf638407839abbd11ba96f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274727
Reviewed-by: Steinar H Gunderson <sesse@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1116955}
--
wpt-commits: a823469856631666460fc713b552103450a70710
wpt-pr: 38644
Automatic update from web-platform-tests
Split out extra mis-matched test
This seems to be causing some conflict in the Accept-CH cache.
Let's move it into its own file and see if the issue persists.
Bug: 1423160
Change-Id: Icfb30645591b041263c827b75566b0658abc3c84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4335564
Commit-Queue: Mike Taylor <miketaylr@chromium.org>
Reviewed-by: Mike Taylor <miketaylr@chromium.org>
Auto-Submit: Ari Chivukula <arichiv@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1116931}
--
wpt-commits: 80b7e5593bb788da1e1142da226dfc3b3df1eeea
wpt-pr: 38979
