Automatic update from web-platform-tests
[@property] Add PropertyRegistry::Version
The version is simply a number that increases monotonically for each
change to the registry. This is needed by the animations machinery to
handle cases where the type of a registered custom property changes
on the fly during an ongoing animation. (See InvalidatableInterpolation
::EnsureValidInterpolationTypes). When the version changes, we can
clear the conversion cache, which causes the keyframes to be
reinterpreted according to the new registration.
Also move some utils from at-property.html to utils.js, for reuse
in other test files.
Bug: 973830
Change-Id: I97d0a37f016ccde649fe1482084707edd123903b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159212
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761323}
--
wpt-commits: 0a970f919e3a8f134f6b8b4cd03e63ef865bd38f
wpt-pr: 23159
Automatic update from web-platform-tests
Wasm: test SharedArrayBuffer-ness in another way (#23112)
--
wpt-commits: 6a1b15e5d699a00d58844b53e8c18d368169018d
wpt-pr: 23112
Automatic update from web-platform-tests
SignedExchange: Extend timeout of two tests
This extends timeout of two WPTs that are flakily timing out on bots:
- sxg-reporting-navigation-parse_error.tentative.html
- sxg-referrer-remote-physical-remote-logical.tentative.https.html
Bug: 1067502,1067264
Change-Id: I94a5fdaa0f4e8cf810438c8fba370300d4f72195
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159386
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761303}
--
wpt-commits: c4d9e7b35b0b011c4f7fc15d618261500efa8c8d
wpt-pr: 23161
Automatic update from web-platform-tests
Scripts moved between documents (#19632)
This follows the changes in https://github.com/whatwg/html/pull/2673, but also tests the issue at https://github.com/whatwg/html/issues/2137 in favor of the current spec.
Co-Authored-By: Domenic Denicola <d@domenic.me>
--
wpt-commits: 299dd665683c2c5a4896bfb7727d8666aa6bba89
wpt-pr: 19632
Automatic update from web-platform-tests
Fix Webxr WPTs
The "is webkit" heuristic only checks that self.internals exists;
however, this is also true on chromium. Chromium however does not have
an "internals.xrTest", this expands the "is webkit" heuristic to also
account for the presence of "internals.xrTest" and thus ensure chromium
tests run
Fixed: 1072929
Change-Id: Ieba043ba1634b393905e4494d0c59294aa6df12b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159320
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761158}
--
wpt-commits: ef350cb9bd09615e8519a6d3ce08b478e4961207
wpt-pr: 23153
Automatic update from web-platform-tests
[@property] Set status to 'test' and move tests to WPT
Bug: 973830
Change-Id: I5d950496834ab17dc8615335c9c4ae25f2a4179b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157528
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761157}
--
wpt-commits: 8ab9b393636f35a1ddeb0526483b9c03013a4f98
wpt-pr: 23134
Automatic update from web-platform-tests
Set up py3-only tools/quic and its venv (#23075)
* [quic] Set up py3-only tools/quic and its venv
This does not include the actual server, but only sets up the skeleton:
* Introduce a "py3only" to commands.json
* Create the skeleton of tools/quic and set up its venv
The plan is to have `wpt serve` call `wpt servequic` (behind a flag).
For more details, see
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/quic.md
* Squashed 'tools/third_party/aioquic/' content from commit 88f258ae47
git-subtree-dir: tools/third_party/aioquic
git-subtree-split: 88f258ae47b7ec85de5ecf4104665054b969a9bb
--
wpt-commits: 4b870dfffeb7031d3657af7a950dd0ea1304bf10
wpt-pr: 23075
Automatic update from web-platform-tests
[lint] Add support for QUIC handlers and tests
* handlers: .quic.py files are Python 3-only so don't try to parse them.
* tests: add "quic" as a valid kind of metadata (note that manifest
support hasn't been implemented yet).
--
Skip tools/quic in py27-flake8
It contains code invalid in Python 2.
Drive-by: rename py36-flake8.ini to py3-flake8.ini as it's used by
multiple Python 3 versions.
--
wpt-commits: 8cdf17f2eca3a8fab82eccbe907627f2052382bd, 1d787b148b6bc65324746339d903c84e653e8ac5
wpt-pr: 23078
Automatic update from web-platform-tests
Rename a bunch of older idlharness test (#23149)
The modern naming convention seems to be to have the test include the
word 'idlharness' in some way, whereas 'interfaces' was the old version.
--
wpt-commits: e00d15c0e09f84bb65588fff9546f80c3721f04b
wpt-pr: 23149
Automatic update from web-platform-tests
[@property] Determine the registration
The current behavior for dealing with multiple registrations on the
same custom property was highly temporary, and not based on any spec.
The spec has since been updated to describe how it should work:
in short, registrations originating from CSS.registerProperty are
stored independently from those originating from @property, and
CSS.registerProperty-registrations (if present) win over @property-
registrations.
Changes in this CL:
- Separates storage for CSS.registerProperty-registrations
(registered_properties_) and @property-registrations
(declared_properties_). The old code put @property registrations
in the same map as CSS.registerProperty-registrations, and only
if no registration exited already. (Meaning for example that the
first @property seen would win---opposite of how it's spec'd to
work now).
- Determines the registration [1] correctly. I.e. first checks the
the CSS.registerProperty-registrations, and the @property ones.
- Adds an iterator which yields the currently active registrations
across both registration types. (I wanted to do this separately,
but initial values won't work properly without it, and there's a
test that relies heavily on that being functional).
Note that it's not explicitly stated in the spec that the storage for
the two registration types shall be separate, but that _is_ the
background for the current spec text on the subject. The rationale is
that it makes it easier to reason about which registration is the
current one when @property rules can appear and disappear via JS.
It's also expected that CSS.unregisterProperty will be added in the
future, making the situation even more unstable.
[1] https://drafts.css-houdini.org/css-properties-values-api-1/#determining-registration
Bug: 973830
Change-Id: I69b48629034b333ebed5d374f943d08b39579334
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157071
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761075}
--
wpt-commits: 7aa1b761a317d924763915d2505f3a500659b47f
wpt-pr: 23135
Automatic update from web-platform-tests
CookieStore: Add validation behavior for __Host- prefixed cookies
This change adds the following checks for "__Host-" prefixed cookies:
1. Disallows overwriting with an explicit domain
2. Disallows non "/" path
This behavior is mentioned in the spec here [1].
Creating a cookie that violates this will cause a crash without
this change.
[1] https://wicg.github.io/cookie-store/#prefixes
Change-Id: I20968f11759019921aa7a6b37602878a17b091ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151825
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760776}
--
wpt-commits: e731ebbe61dc7cd861633585c704fb59bde64b9f
wpt-pr: 23026
Automatic update from web-platform-tests
Screen Enumeration: Add a placeholder Screen.id to replace Screen.name
Use placeholder ordinal ids for now (0, 1, 2, ...); update tests.
TODO: generate per-origin UUIDs that reset when cookies are deleted
Test Screen.id values returned via window.getScreens() with:
chrome://flags#enable-experimental-web-platform-features OR
$ chrome --enable-blink-features=ScreenEnumeration
Try https://michaelwasserman.github.io/window-placement-demo
Bug: 994889
Test: Automated, Screen.id placeholder values
Change-Id: I0c5b18b92fef251211822f3473ea85472a7ee945
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155113
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761040}
--
wpt-commits: f8d36b93adcfb21622c935a77427bf99caf3d1e3
wpt-pr: 23082
Automatic update from web-platform-tests
Animations modified with setKeyframes must not mask !important
CSS declarations that are !important have higher priority in the
cascade than animation effects. Unfortunately the information about
which declarations were and weren't important is lost once the
StyleCascade disappears. Specifically, it's not stored on the
ComputedStyle. This causes a problem (once again) for the base computed
style optimization, since we can't naively add animation effects on
top of the base anymore. We might be overwriting something in the base
that was important.
The previous attempt at fixing this (flag on ElementAnimations) doesn't
work properly. For example, it fails to detect the case where an
animation initially doesn't conflict with important declarations, but
then suddenly does via setKeyframes.
To solve this, this CL stores a bitset containing information about
important declarations alongside the base ComputedStyle on
ElementAnimations. When we're considering whether the base can be used
or not, we then check if there's any animation matching the set of
important declarations.
Persisting that many bits is slightly uncomfortable, but the only
viable alternative I see is disabling the optimization when *any*
important declaration exists in the base, which is probably a worse
option.
Sidenote: Initially I tried to always use the base, even when there
were conflicts with important declarations. The bitset of important
declarations is effectively a set of animations to be skipped, so we
should still be able to use the base if we just don't apply the
properties present in the set. However, it unfortunately didn't work
due to visited/unvisited colors being animated together
(crbug.com/1062217).
Bug: 552085
Change-Id: I39e2879af8a858ce1bd97eaa2ceb6e222591df79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152449
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761034}
--
wpt-commits: 9f16de83abdee864d6dafebbacc298b08964750d
wpt-pr: 23032
Automatic update from web-platform-tests
Replace assert_precondition with assert_implements in vibration/ (#23022)
assert_precondition is deprecated (see
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/assert_precondition_rename.md).
Since navigator.vibrate is not an OPTIONAL part of the Vibration API
spec, this test should use assert_implements.
--
wpt-commits: 440e3632f10aadb0fc0f90c923ca6b6467887fd8
wpt-pr: 23022
Automatic update from web-platform-tests
Add more references to sticky position ref tests
This is a follow-up patch of
https://chromium-review.googlesource.com/c/chromium/src/+/2105754
This patch adds more reference rectangles to sticky ref-tests to catch
when the main thread position is different from the sticky position.
Bug: 1059272
Change-Id: Ib3101e58a95db134a427b2852bca4c4bd58f805e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2137828
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761027}
--
wpt-commits: 9586cd0785957c1f58c58cc9df9bc7410ffe8aff
wpt-pr: 22752
Automatic update from web-platform-tests
[WPT] Fix paths in svg-image-orientation.html and ref
When this test was landed, a file move was not reflected in the
paths to resources. Fix it.
TBR: fs@opera.com
Change-Id: I6b1df77d11c63e657369e681f52d9091b27b428a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159305
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760934}
--
wpt-commits: 083c17b74c10722fed558dfb5bb26b4956be5a1d
wpt-pr: 23139
Automatic update from web-platform-tests
[cssom] Add a test for enumeration of logical props in getComputedStyle.
Also test environment variables because webkit exposes them.
--
wpt-commits: 6cb7fa4dd30e1f9e2c303a49dad2ba9b4a5d76b1
wpt-pr: 23088
Automatic update from web-platform-tests
Make transition in FCP test faster, otherwise test is slow (#23132)
Co-authored-by: Noam Rosenthal <noam@webkit.org>
--
wpt-commits: c1bc664ebc3bd5132eb57727f7656c8c82444fec
wpt-pr: 23132
Automatic update from web-platform-tests
[css-flexbox] Move fixedpos-video-in-abspos-quirk-crash.html to WPT
Migrate this test out of third_party/blink/web_tests/css3/flexbox
and into the WPT-specific directory, adding links to the relevant
specs and a test assertion describing its purpose.
Bug: 1063749
Change-Id: I89f11b01b18f3b4f1bcc58c6578ed24cdcc2ff6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153460
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#760799}
--
wpt-commits: 9a6026305062c90d84a567d81434010dde6c6c22
wpt-pr: 23051
Automatic update from web-platform-tests
Fix inline box positions when RTL and has trailing spaces
This patch fixes inline box positions when the line is in RTL
and has preserved trailing spaces.
Two issues were found for this case:
a. Computes incorrect value for how much the line hangs.
b. When hang is not zero, inline box positions are incorrect.
This patch fixes the issue b.
The issue a is related but does not contribute to the
reported symptom. It should be worked with better trailing
space support and UAX#9 L1 support (crbug.com/316409). TODO
comment added for this issue.
Bug: 1062716
Change-Id: Ie33db517ebc886a724116b594699f8d59751c808
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2156235
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760793}
--
wpt-commits: 44215ed1f182054fdd55a43035b70041b50d61b0
wpt-pr: 23119
Automatic update from web-platform-tests
[css-logical] Include logical properties when iterating a computed style
The logical properties were not added into kComputedPropertyArray, so
they were skipped when iterating a computed CSSStyleDeclaration like
[...getComputedStyle(document.body)].
BUG=1072180
TEST=external/wpt/css/css-logical/getComputedStyle-listing.html
TEST=external/wpt/css/cssom/cssstyledeclaration-csstext.html
TEST=external/wpt/css/cssom/cssstyledeclaration-custom-properties.html
TEST=fast/css/getComputedStyle/computed-style-listing.html
TEST=fast/css/getComputedStyle/computed-style-without-renderer-listing.html
TEST=svg/css/getComputedStyle-listing.html
Change-Id: Ia83ac8608b2b98601f454653900e76f89291b4aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153442
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#760732}
--
wpt-commits: 17b3f85c94583270571b8b8e4a8815d664dbb1c8
wpt-pr: 23125
Automatic update from web-platform-tests
Fix customized built-in element constructor behavior
This CL implements two changes:
1. It fixes the implementation to better match the spec for the
"create an element for the token" [1] algorithm. Prior to this CL,
step 7 of that algorithm was skipping directly to step 6 of the
"create an element" [2] algorithm, skipping over step 5 for
customized built-in elements. This is now fixed. This case is
illustrated by the issue and example at [3] and [4]. This becomes
the first test in customized-built-in-constructor-exceptions.html.
2. It updates the comments to match the new behavior discussed in [3]
and the [5] spec PR, which changes the return value in the case
that a customized built-in element constructor throws an exception.
With the change above, that is actually already the behavior. So
this is just a comment change. Two new tests are added to
customized-built-in-constructor-exceptions.html.
[1] https://html.spec.whatwg.org/multipage/parsing.html#create-an-element-for-the-token
[2] https://dom.spec.whatwg.org/#concept-create-element
[3] https://github.com/whatwg/html/issues/5084
[4] https://crbug.com/1024866
[5] https://github.com/whatwg/dom/pull/797
Bug: 1071059, 1024866
Change-Id: I814c81991eb5e83501304bcb3d2da476743aef52
Cq-Do-Not-Cancel-Tryjobs: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152986
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760705}
--
wpt-commits: 8086723599f2bcdcbf54bcecff8cc50038cf939a
wpt-pr: 23072
Automatic update from web-platform-tests
Add a test for unexpected activation triggered during space keydown driven focus management (#22424)
Relevant spec: https://w3c.github.io/uievents/#event-flow-activation
This is targeting a Firefox bug where when forwarding focus on space and enter
keydown events, a unexpected click event is triggered on the forward target.
Here's a demo page for the buggy behavior:https://html-is.glitch.me/firefox-space-focus.html
This test case only cover the Space key case where Firefox is the outlier.
--
wpt-commits: cc87c188abc5c88460d24379e69d540372f0c683
wpt-pr: 22424
Automatic update from web-platform-tests
Add WebKit support for WebXR tests (#23031)
WebXR and the WebXR testing API are in the process of being implemented. The way we designed the integration of the test API with the rest of the engine is by adding WebXRTest to an object called Internals which is injected in JSC and that provides JS access to WebKit's internal APIs. That Internals object is only available for testing so we can ensure that WebXRTest is never exposed to the Web.
--
wpt-commits: 603ea91ccada76c2796bc51d1cf027882582cd83
wpt-pr: 23031
Automatic update from web-platform-tests
Rework WPT: /fetch/stale-while-revalidate/stale-image.html
Previous patch:
https://chromium-review.googlesource.com/c/chromium/src/+/2154786
improves ./stale-script.html
For consistency and because the test looks slightly nicer, this patch
applies the same kind of refactoring to ./stale-image.html
Bug: 1070117
Change-Id: Idae5a373154d9f6e8cc63d054d3abfe2662b621e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152797
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760574}
--
wpt-commits: fddc3a878fbc036ae2c5d9cda328814e8c0f4f60
wpt-pr: 23068
Automatic update from web-platform-tests
Rework WPT: /fetch/stale-while-revalidate/stale-css.html
Previous patch:
https://chromium-review.googlesource.com/c/chromium/src/+/2152797/1
improves ./stale-image.html
For consistency and because the test looks slightly nicer, this patch
applies the same kind of refactoring to ./stale-css.html
Bug: 1070117
Change-Id: I5a30c105aca4c2bde0962004f9a97e4fbde2ab4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152798
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760552}
--
wpt-commits: c07b77f5e6844e49972496a5ec5d8c19e114a7d7
wpt-pr: 23067
Automatic update from web-platform-tests
Rework WPT: /fetch/stale-while-revalidate/stale-script.html
Mainly for improving my own understanding. I would like to make some
tests about CSP vs stale-while-revalidate for issue 1070117
This patch:
1) Use Promise(s) instead of callback(s). This unwrap the logic flow.
2) Make "last_modified_count" to count the number of new version being
served. Previously, it was a bit confusing to me.
3) Extend the test to check the "revalidated" version is served on the
3rd load.
4) Small misc refactorings.
Bug: 1070117
Change-Id: Ifba23d78e539eb50262244f59e7c16e1b9ca56ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154786
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760550}
--
wpt-commits: 786254638cb557073634ba37262f31668712df4b
wpt-pr: 23069
Automatic update from web-platform-tests
Pass a protocol to the TimedRunner constructor instead of a session.
--
wpt-commits: 13231f31e635216979d3cba401f31d929d89ba95
wpt-pr: 23120
Automatic update from web-platform-tests
MIME Sniffing: tests for MIME type groups
Note: these are currently not run by browsers, but might be useful for tooling.
--
wpt-commits: 5c417eadfaa7ff328eb1cbc6338b843d73de4f63
wpt-pr: 23116
Automatic update from web-platform-tests
[blink] Add tests for destructive writes with JavaScript modules (#22723)
* [blink] Add tests for destructive writes with JavaScript modules
This adds test for document.write in different situations with
modules that were previously not tested or documented to the same
extent.
This also adds a test for future top-level await implementation.
- JavaScript proposal: https://github.com/tc39/proposal-top-level-await
- HTML proposal: https://github.com/whatwg/html/pull/4352
Bug: 1022182, v8:9344
Change-Id: I873df1e6aab2aa1ac6f7bf1b842059053f4a7cc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134132
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760411}
Co-authored-by: Camillo Bruni <cbruni@chromium.org>
Co-authored-by: Stephen McGruer <smcgruer@chromium.org>
--
wpt-commits: 3a31f9c2822c84b2cbad5287a41c42c8ecbd7708
wpt-pr: 22723
moz-wptsync-bot
Anders Hartvoll Ruud
Anne van Kesteren
Kunihiko Sakamoto
hiroshige-g
Alexander Cooper
Robert Ma
Stephen McGruer
Ayu Ishii
Mike Wasserman
autofoolip
haozhe
Stephen Chenney
Majid Valipour
Emilio Cobos Álvarez
Noam Rosenthal
Julie Jeongeun Kim
Koji Ishii
Oriol Brufau
Mason Freed
Mu-An 慕安
Sergio
Yi Xu
arthursonzogni
Antonio Gomes
Josh Matthews
J. King
Blink WPT Bot