Automatic update from web-platform-tests
[scroll-animations] Support animation-timeline:none
Parsing of the 'none' keyword was already supported, so this CL
simply connects the dots between the parsed timeline name
and the timeline we pass to the CSSAnimation.
For the InertEffect, the inherited_time now needs to be a base::nullopt
to prevent an effect value from being produced, so a small adjustment
was needed there.
Note: Changing from IsScrollTimeline() to IsMonotonicallyIncreasing()
is just a cosmetic change.
Note also that the test animation-timeline-in-keyframe.html required
a small adjustment: previously, the computed value of animation-timeline
was 'bar', but there was no @scroll-timeline corresponding to 'bar',
so according to spec the animation has no timeline in this case,
and therefore no effect value [1]. We previously fell back
to the DocumentTimeline, which is not correct: we should have fallen
back to "no timeline", which is what we do as of this CL.
[1] https://drafts.csswg.org/css-animations-2/#animation-timeline
Bug: 1074052, 1097046
Change-Id: Ia664f92f70dff68a17eb82315d6bb7bf18de79f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367835
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801363}
--
wpt-commits: 1a64643e528b76e668b8d52f8f35b7a1e68304d6
wpt-pr: 25229
Automatic update from web-platform-tests
[fetch] Empty destination should be the empty string, not "empty"
As specified at [1],the empty destination should be the empty string,
not "empty". We use "empty" for the "sec-fetch-dest" header[2] though.
Fix the implementation and fix incorrect WPTs altogether.
1: https://fetch.spec.whatwg.org/#concept-request-destination
2: https://w3c.github.io/webappsec-fetch-metadata/#abstract-opdef-set-dest
Bug: 1121493
Change-Id: Ia86d716dd434c3b6b0e6f1914019fd6110a7ab8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2374725
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801368}
--
wpt-commits: a05058d027c17c6863b1c3a4610dae0d2ab58876
wpt-pr: 25224
Automatic update from web-platform-tests
Change offscreen commit to be an async test (#24999)
The first test case uses setTimeout to release the event loop and does
some asserts inside its callback. This causes the test to register as
PASS despite actually failing and logging just a console message.
--
wpt-commits: 232019eaf60a11179e8603e64d9c9a0f23a496a3
wpt-pr: 24999
Automatic update from web-platform-tests
Correct waiting for negotiationNeeded in test
The test RTCRtpTransceiver.https.html was written wrong.
Bug: chromium:1115087
Change-Id: If6961ac8ec33605ecf97da10d97e4c35281cc6cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2374446
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801307}
--
wpt-commits: 9d4fda1ca06d52bd0f22dbc7660452622a65b2cc
wpt-pr: 25222
Automatic update from web-platform-tests
Rename OverrideBuiltins to LegacyOverrideBuiltins.
This CL rename Web IDL |OverrideBuiltins| to |LegacyOverrideBuiltins| to
make its usage more clear.
Bug: 1072773
Change-Id: I0068fe21136dc3ccf68c5a34e293fffab99a3ec3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359880
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Cr-Commit-Position: refs/heads/master@{#801298}
--
wpt-commits: 72b58ec0a9689a58a7d71cd2d7f07705feacbe1e
wpt-pr: 25089
Automatic update from web-platform-tests
Don't use DefaultCacheIdentifier while loading resources from WebBundle
This CL changes ResourceFetcher::GetCacheIdentifier() to use the
bundle's URL as the cache identifier, when the resource is listed in the
resource= attribute of <link rel="webbundle">,
Bug: 1082020
Change-Id: I2035f9ef37bf40c8a636baecf38031ed1a585813
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2371424
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801276}
--
wpt-commits: b1149b30e0389b3c4d2b17bb12201b57adda09d8
wpt-pr: 25206
Automatic update from web-platform-tests
[webcodecs] Dictionary based ctors for encoded video and audio chunks
Bug: 1120732
Change-Id: I5676235f316e64183f95b2e33b24317c868d18e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368470
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801201}
--
wpt-commits: 8dfc8865885820d153c9d9a0cf3196e75338c882
wpt-pr: 25201
Automatic update from web-platform-tests
[wptrunner] Skip h2 tests if h2 is not enabled (#25108)
Previously we would try to run h2 tests even if the h2 server was not
enabled. This would lead to marionette crashing when it tried to load a
URL that wouldn't respond.
Fixes https://github.com/web-platform-tests/wpt/issues/25012
Co-authored-by: Robert Ma <robertma@chromium.org>
--
wpt-commits: 5ada3c29a6f8f836d97e8dd6a007086ab1b79fcc
wpt-pr: 25108
Automatic update from web-platform-tests
[scroll-animations] Allow null source in ScrollTimeline constructor
The spec was recently updated to differentiate between the source
being missing and the source being null. The former means that the
source should default to document.scrollingElement, and the latter
means that there is no source.
Note: In the CSS API, this translates to 'auto' and 'none',
respectively. Support for this has already landed in a previous CL.
Bug: 1100907
Change-Id: I1436b16d06b7a7ae0de55e2706a7b5d87c0290b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367837
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801085}
--
wpt-commits: a56629098526c58c4af7744257630cb9483ee902
wpt-pr: 25207
Automatic update from web-platform-tests
Fix mouse-pointer-preventdefault for Firefox/Safari
Safari and Firefox fire pointerevents & compatible mouse
events in a different order than Chrome. The order matches the
PointerEvents specification for all browsers. Modify the test to
reflect this difference in the browser implementation.
Bug: 1085549, 1085647
Change-Id: I43ed0bbbabb0abbcbd93fbab7e5d8ee98a902611
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359588
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801077}
--
wpt-commits: feec911ab56246f8ab1edadde13a686c635a90c4
wpt-pr: 25056
Automatic update from web-platform-tests
Reland "Support triple click in Chromedriver PerformActions"
When we are using PerformActions from ChromeDriver to simulate three
mouse click, it only set the click count to 2, not 3, so this test fails
third_party/blink/web_tests/external/wpt/webdriver/tests/perform_actions
/pointer_tripleclick.py.
PerformActions should keep the mouse click count and decide if we should
increase the count or set to 1 when we have a mouse press based on the
interval of two mouse presses and difference between the current mouse
positions and the last one.
We should keep the click count in the session, and calculate the new
click count based on the count stored in the session.
Bug: 1119679
Change-Id: Iadac8e0f7dd13aebad6dc06c48c572426709a065
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368335
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801082}
--
wpt-commits: 6484354f7ec5c70b6d6af299f429a658370f06df
wpt-pr: 25212
Automatic update from web-platform-tests
[Document Policy] Mark reporting tests on experimental features tentative
Change-Id: I29503665e09272500b6f184c726beadb65bd6a2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367712
Commit-Queue: Charlie Hu <chenleihu@google.com>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801068}
--
wpt-commits: ce4dc497fa602baccfd3123a33081071118a7239
wpt-pr: 25209
Automatic update from web-platform-tests
Quota: Add tentative to WPT name.
Quota Change event is not yet spec'd, so this change updates
the name to reflect that.
Change-Id: I6a4f1bba1bdece6efd577cba39fb2a0ca8b5ee57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369256
Auto-Submit: Jarryd Goodman <jarrydg@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#801046}
--
wpt-commits: 6dbd67e0fb18a2d6defc80a8789c26bd9b1e5b06
wpt-pr: 25194
Automatic update from web-platform-tests
[Docs] Improve advice on using `promise_test`
Mixing the "callback" and "Promise" paradigms makes tests harder to
write and to read. Encourage authors to minimize the overlap (and thus
the potential for error).
--
wpt-commits: 26f68caaea587e99abb28f824a70f7e3a171e0ce
wpt-pr: 25210
Automatic update from web-platform-tests
Add WPT tests for registerProtocolHandler and 'web+' schemes
This is a follow-up of [1] where the validation on the web and browser
processes have been unified. Tests for 'web+' have been added to
ProtocolHandlerRegistryTest (browser process). This CL adds similar and
more complete checks to the existing WPT test (web process).
The relevant section from the specification says [2]:
* Set scheme to scheme, converted to ASCII lowercase.
* If scheme is neither a safelisted scheme nor a string starting with
"web+" followed by one or more ASCII lower alphas, then throw a
"SecurityError" DOMException.
Bug: 971917, 952974, 627682
[1] https://chromium-review.googlesource.com/c/chromium/src/+/2362802
[2] https://html.spec.whatwg.org/multipage/system-state.html#normalize-protocol-handler-parameters
Change-Id: I769048bd4db6883a75d4237f20f23aa61452d732
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2371632
Reviewed-by: Gyuyoung Kim <gyuyoung@igalia.com>
Commit-Queue: Frédéric Wang <fwang@igalia.com>
Cr-Commit-Position: refs/heads/master@{#801004}
--
wpt-commits: 7aedaa1171fe98e83b3cc6876ce4c6ba631645be
wpt-pr: 25208
Automatic update from web-platform-tests
[SanitizerAPI] Change function name to match latest discussion
Reference: https://github.com/WICG/sanitizer-api/issues/22
Bug: 1116418
Change-Id: Iae2fb7bfea173cc0aad35df5b573b5d2fecfac2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367864
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Commit-Queue: Yifan Luo <lyf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800945}
--
wpt-commits: 5ec1a57611718afc77892fbda83e159c158d277e
wpt-pr: 25184
Automatic update from web-platform-tests
Add tests for request headers created by fetch modes
For https://github.com/whatwg/fetch/issues/722.
--
wpt-commits: b31e376852559c36ad32f93aaf08dcdb3b8a413c
wpt-pr: 24662
Automatic update from web-platform-tests
Subresource WebBundles: Same-origin restriction
This patch restricts subresource loading from WebBundles only to
same-origin resources, i.e. origin of subresource URL must be
same-origin with the origin of the enclosing WebBundle's URL.
Bug: 1120252
Change-Id: Ic999c4582385560f22a1251c37bd3572f0ffd2bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368618
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800907}
--
wpt-commits: aa022e797e89bbc1c2f607970efaf3313bbcf386
wpt-pr: 25176
Automatic update from web-platform-tests
docs: Add an example to the t.step_func() + promise_test() section.
Try to make it clearer that `t.step_func()` is needed in event handlers in a
`promise_test()` following the discussion in #25043.
--
wpt-commits: e2a0d6335066eb4cd8dd8e9023daaf9afea36216
wpt-pr: 25202
Automatic update from web-platform-tests
Will-change: opacity should create a stacking context for inlines
The spec [1] states that will-change: opacity should create a stacking
context for inlines in the same way that non-zero opacity does. This was
fixed by https://crrev.com/776581 ("Unify CSS grouping properties") but
we didn't have a testcase. This patch adds a WPT test of this behavior.
[1] https://drafts.csswg.org/css-will-change/#will-change
Bug: 1119651
Change-Id: I7abd4006b61039d9302f8ac9036848aeb37df476
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2370095
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Auto-Submit: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800845}
--
wpt-commits: 7ba10964e8b78acca1a540f4b1f42dad6841276f
wpt-pr: 25200
Automatic update from web-platform-tests
WPT: Service Worker: Add unexpected state check to wait_for_state() (#24933)
This patch makes wait_for_state() in test-helpers.sub.js for a service
worker WPT test check an unexpected state after adding the event
handler. Before this patch, wait_for_state() only checks the equivalence
of the state to the specific state. It might wait forever if the worker
unexpectedly skips the state or it's unexpectedly evicted.
Bug: 1000544
Change-Id: I7025fad3ba25648888a762e16ae0ded63f9c4f9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344440
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799561}
Co-authored-by: Yuta Kasai <kasai.yuta0810@gmail.com>
--
wpt-commits: a28628a7f1cec962767531f77172bb93d77e6b44
wpt-pr: 24933
Automatic update from web-platform-tests
Allow range requests to pass through a service worker (#25053)
This change implements the following edits to the Fetch spec:
https://github.com/whatwg/fetch/pull/560https://github.com/whatwg/fetch/pull/1076
Existing web tests cover the new functionality.
Bug: 847428
Change-Id: Ie63704769e99d4b8d26d8903edf4cc4e3466c124
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339761
Commit-Queue: Nicolas Arciniega <niarci@microsoft.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800663}
Co-authored-by: Nicolas Arciniega <niarci@microsoft.com>
--
wpt-commits: 868ca3586f9dda74b2bb3b6f6dfb67a13e359090
wpt-pr: 25053
Automatic update from web-platform-tests
[css-flex] Use definite cross size and aspect ratio for flex base size
When an aspect-ratio item has a definite cross size, we are supposed to
compute the flex base size by multiplying those two. Blink did this when
the item had a computed definite cross size, but not when the item had a
definite cross size due to stretching.
Firefox has the same bug.
The modified canvas test relied on the buggy behavior. The tests we now
fail also assert the buggy behavior, but are only one-way synced from
mozilla's repository, so we can't change them.
This fix is behind a flag.
Bug: 704294
Change-Id: Ie17c451c7ec81ccb36fb96ff1543885bd7352bcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368321
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800801}
--
wpt-commits: 9503a10b444a62efb325d2b5d5ec393a0188e0ed
wpt-pr: 25195
Automatic update from web-platform-tests
Audio|VideoDecoderBroker: more weakptr, keep callbacks on main thread.
Using unretained for decoder/selector callbacks is generally not safe /
fragile. For ex, some decoders (e.g. those that offload) will call the
output callback after destruction. Another example: decoder selector
internally posts the Select() callback, so it may run after destruction.
Additionally, sending incoming callbacks as CrossThreadFunctions for
invoking on the media thread is not safe. We may destruct while some
callbacks are still pending, destroying the callbacks internal state
(including bindings to blink GC types) off the main thread. Now we
ensure that all callbacks are saved on the main thread and we extend
the "client" interfaces of the broker for proxying the callbacks safely.
Bug: 1120431
Change-Id: I2ccfe46982cda9b18e47a56424b25f54f8877883
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366661
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Auto-Submit: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800776}
--
wpt-commits: f32b898cd57d5dc50cfd4692e6145677358bf50b
wpt-pr: 25185
Automatic update from web-platform-tests
wpt: Fix the content-visibility test to reflect sync-auto observation.
The spec has changed to ensure that 'auto' content-visibility
intersection observations are synchronous (after lifecycle) on the
first frame.
The test change is to expect new behavior as well as test previous
behavior by making a container off-screen first.
R=chrishtr@chromium.org, jarhar@chromium.org
Change-Id: I0ef3182b04a2a8731a80a044689581f2a5ac3c2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368509
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800669}
--
wpt-commits: 81e5ffd05b7a2676e5b4d080c6566e890636a494
wpt-pr: 25191
