Граф коммитов

704833 Коммитов

Автор SHA1 Сообщение Дата
youennf 656db73af8 Bug 1632477 [wpt PR 23202] - Add a test checking that deviceId is empty before getUserMedia is called, a=testonly
Automatic update from web-platform-tests
Add a test checking that deviceId is empty before getUserMedia is called (#23202)

* Add a test checking that deviceId is empty before getUserMedia is called

* Add test for number of exposed devices before capture
--

wpt-commits: 2d95f2025c31214e6e5747816496d5867646969c
wpt-pr: 23202
2020-04-30 19:03:40 +00:00
moz-wptsync-bot ffa531a627 Bug 1630530 [wpt PR 22990] - Update wpt metadata, a=testonly
wpt-pr: 22990
wpt-type: metadata
2020-04-30 19:03:40 +00:00
Asami Doi a27b89ff88 Bug 1630530 [wpt PR 22990] - wpt: Add WPT tests for navigation preload and same site cookies., a=testonly
Automatic update from web-platform-tests
wpt: Add WPT tests for navigation preload and same site cookies.

WPT tests to check if the navigation request handled by navigation
preload contains cookies in its headers. There are 3 tests depending on
the `SameSite` attribute.

Bug: 920488
Change-Id: I0a2c539443f9216c7d5fabd714e9cf4a3ff3d0a7

--

wpt-commits: 79617e1f06ebb131e7c816d519c11192b7c63930
wpt-pr: 22990
2020-04-30 19:03:39 +00:00
Rob Buis a3ad77bdf1 Bug 1631704 [wpt PR 23131] - Wait for resource to be fetched completely, a=testonly
Automatic update from web-platform-tests
Wait for resource to be fetched completely (#23131)

Wait for resource to be fetched completely before comparing headers, since
some implementations only cache when the complete resource is fetched, rather
than just the first response, and this test relies on caching the first fetch.
--

wpt-commits: f98b6fb53c68797b35c5268e039f4a7b19df9411
wpt-pr: 23131
2020-04-30 19:03:39 +00:00
Mason Freed b4b75f6c1c Bug 1632383 [wpt PR 23195] - Add a test for declarative Shadow DOM after attachShadow(), a=testonly
Automatic update from web-platform-tests
Add a test for declarative Shadow DOM after attachShadow()

This is a new test to verify that declarative shadow DOM (properly)
fails if attachShadow() has already been called on the host node.

Bug: 1042130
Change-Id: Ibca94f9be5f6a1eb3c3bdd491f84e782e8cc6d9f

--

wpt-commits: 84f93271efe15a4e37fed477a2ad364f8659a0f8
wpt-pr: 23195
2020-04-30 19:03:38 +00:00
moz-wptsync-bot 56f7c826b4 Bug 1631513 [wpt PR 23121] - Update wpt metadata, a=testonly
wpt-pr: 23121
wpt-type: metadata
2020-04-30 19:03:38 +00:00
Anne van Kesteren e550f4da9f Bug 1631513 [wpt PR 23121] - Meta: remove need for !worker in workers/ tests, a=testonly
Automatic update from web-platform-tests
Meta: remove need for !worker in workers/ tests

Helps with #23111.

--

wpt-commits: b7f09dc81131e15c19fec3a9e198257f9bc9b43e
wpt-pr: 23121
2020-04-30 19:03:37 +00:00
Kevin Ellis 5ac2e54f6c Bug 1632310 [wpt PR 23186] - Add test for computed versus resolved style., a=testonly
Automatic update from web-platform-tests
Add test for computed versus resolved style.

Change-Id: I3b05d556f011ecca39b4573516c4c39d2ec1b415

Bug: 1057307
Change-Id: I3b05d556f011ecca39b4573516c4c39d2ec1b415

--

wpt-commits: db694b482439296306f64f26db16c58d46e4695a
wpt-pr: 23186
2020-04-30 19:03:37 +00:00
Piotr Bialecki f31853fa4e Bug 1631648 [wpt PR 23126] - WebXR - AR - adjust XRRay to match the spec, a=testonly
Automatic update from web-platform-tests
WebXR - AR - adjust XRRay to match the spec

Bring XRRay up to spec, adjusting the behavior with changes introduced
by PR:
https://github.com/immersive-web/hit-test/pull/85

Additionally, fix Chrome's Web IDL to not rely on overloads.

Change-Id: I98af1a4ed90dbeb8e311795e818efb64bb15034d

--

wpt-commits: fd045759df43fa155b34a5e4fe4187610ad1bb24
wpt-pr: 23126
2020-04-30 19:03:36 +00:00
moz-wptsync-bot 120c5940e1 Bug 1632171 [wpt PR 23168] - Update wpt metadata, a=testonly
wpt-pr: 23168
wpt-type: metadata
2020-04-30 19:03:36 +00:00
Anders Hartvoll Ruud 8fc2bb6f33 Bug 1632171 [wpt PR 23168] - [@property] Mark for recalc when removing declarations, a=testonly
Automatic update from web-platform-tests
[@property] Mark for recalc when removing declarations

I forgot to notify StyleEngine when the property registry changes
due to declarations being cleared. This meant removals would not
take effect correctly/predictably.

Since CSS.registerProperty / @property use the pattern of static
methods on PropertyRegistration to do some work + notifying
StyleEngine, we can follow the same pattern for this case.

Also rename CustomPropertyRegistered to PropertyRegistryChanged.

Bug: 978780, 973830
Change-Id: I3bd03f548a7783f1270d823501e4bf9b1c0778e6

--

wpt-commits: cd987667984a6d28c51e6335535c3e585c7e4ee1
wpt-pr: 23168
2020-04-30 19:03:36 +00:00
Yoav Weiss 37ec34b504 Bug 1633704 [wpt PR 23087] - [server-timing] Populate values for NavigationTiming, a=testonly
Automatic update from web-platform-tests
[server-timing] Populate values for NavigationTiming

Currently, Navigation Timing's Server Timing values are populated when
the entry is first created, which happens when it is first queried. For
long documents, that can happen before the body is loaded, which is the
point in which the response is set on the NavigationTiming entry's
TimingInfo.
This CL fixes that, by setting the response on the TimingInfo earlier,
at the document's commit time.

Change-Id: I10522342a7d92560167bdb7d33956823e588d9d8

Bug: 1068937
Change-Id: I10522342a7d92560167bdb7d33956823e588d9d8

--

wpt-commits: 0084aa71d4d4935fcbb43bd8122328da9d305098
wpt-pr: 23087
2020-04-30 19:03:35 +00:00
Hongchan Choi 6441e81375 Bug 1631985 [wpt PR 23158] - Correct input connection and automatic pull behavior of AudioWorkletNode, a=testonly
Automatic update from web-platform-tests
Correct input connection and automatic pull behavior of AudioWorkletNode

This CL fixes a failing test (process-parameters.https.html) and
it needs two changes in AudioWorkletNode:

1. Handling of unconnected inputs:
  - spec: https://webaudio.github.io/web-audio-api/#dom-audioworkletprocessor-process-inputs-outputs-parameters-inputs
  - "If there are no actively processing AudioNodes connected to
     the 𝑛th input of the AudioWorkletNode for the current render
     quantum, then the content of inputs[n] is an empty array,
     indicating that zero channels of input are available."
  - Thus, if an input is not connected, it will have an array with
    zero element. (length == 0)

2. Handling of automatic pull:
  - The implementation did not have a proper automatic pull
    functionality for AudioWorkletNode. Without connect() or
    disconnect() call the node will not be automatically pulled.

This change introduces failures in the "active processing" tests,
because those tests are expecting non-zero channel count for the
unconnected input:

  - the-audiobuffersourcenode-interface/active-processing.https.html
  - the-channelmergernode-interface/active-processing.https.html
  - the-convolvernode-interface/active-processing.https.html

I prefer to mark 3 tests above "failure", and handle them later in
a separate patch.

Bug: 1046516
Test: the-audioworklet-interface/process-parameters.https.html
Change-Id: I55f9a1b6eb88c172a8d050598c6e5f946fe9692b

--

wpt-commits: e764b34bd01c8ed11efeb9205589dc4dbf09cf54
wpt-pr: 23158
2020-04-30 19:03:35 +00:00
Nicolás Peña Moreno 5b2ce62944 Bug 1632253 [wpt PR 23180] - Reland "[EventTiming] Add shadow DOM test for first input", a=testonly
Automatic update from web-platform-tests
Reland "[EventTiming] Add shadow DOM test for first input"

This is a reland of 9591b7074cacf1e8aeb9082dee2a4f46a171083f

Original change's description:
> [EventTiming] Add shadow DOM test for first input
>
> This CL tests event.target for first-input. The DOM elements do not have
> event listeners to show that event retargetting correctly retargets to
> the shadow host.
>
> Bug: 543598
> Change-Id: Ibd5a4a37a50f79b86d93a5c9c18c8ac7300ba723
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159622
> Reviewed-by: Steve Kobes <skobes@chromium.org>
> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#761417}

Bug: 543598
Change-Id: I21537ddc47075a5f0acaf0b53662b4db242c66a0

--

wpt-commits: 2a3389554f038ed396be6f699414aad23e7fe581
wpt-pr: 23180
2020-04-30 19:03:34 +00:00
moz-wptsync-bot d2976ff5d2 Bug 1632172 [wpt PR 23169] - Update wpt metadata, a=testonly
wpt-pr: 23169
wpt-type: metadata
2020-04-30 19:03:34 +00:00
Anders Hartvoll Ruud df0264d290 Bug 1632172 [wpt PR 23169] - [@property] Initial should be required for non-universal syntax, a=testonly
Automatic update from web-platform-tests
[@property] Initial should be required for non-universal syntax

 - Require an initial value for the @property rule to be valid.
   (Except universal syntax definitions).
 - Rename IsTokenStream -> IsUniversal. (It's nice to have names that
   match the spec concepts).
 - Fix typo 'initalValue' in an otherwise unrelated test.

Bug: 973830
Change-Id: I675f0c46b7918e4a81287d600d977ff76484cf8b

--

wpt-commits: 959a0d091354d3cb78d71c00a418092f29ce9857
wpt-pr: 23169
2020-04-30 19:03:33 +00:00
moz-wptsync-bot 659cf82b2c Bug 1632174 [wpt PR 23170] - Update wpt metadata, a=testonly
wpt-pr: 23170
wpt-type: metadata
2020-04-30 19:03:33 +00:00
Carlos Alberto Lopez Perez 1e0c9fa446 Bug 1632174 [wpt PR 23170] - css-flexbox: convert 7 manual-tests to ref-tests, a=testonly
Automatic update from web-platform-tests
css-flexbox: convert 7 manual-tests to ref-tests (#23170)

* This converts the css-flexbox align-content_*.html tests and
flexbox-order-only-flexitems.html test to ref-tests.

* css-flexbox/align-content_space-around.html change height to 210:
that way the numbers of the ref-test spacer become 20 and 10 and
are perfectly round avoiding possible problems with subpixel layout.

--

wpt-commits: b3cc52b6cfaa5b6852bf9b07e62d007ab142ffa9
wpt-pr: 23170
2020-04-30 19:03:32 +00:00
Ian Kilpatrick 98a44f320e Bug 1632238 [wpt PR 23178] - [FlexNG] Add test for replaced %-block-size descendant., a=testonly
Automatic update from web-platform-tests
[FlexNG] Add test for replaced %-block-size descendant.

With FlexNG we now cache on the ComputeMinMaxSizes level.
This fixes a subtle dynamic edge case.

Previously (legacy) wouldn't invalidate the flex-item base size due to
a parent height changes.

This adds a test for this case.

Bug: 845235
Change-Id: Ic711c3f8110b08fcc89351274a7bd283f66c1ce1

--

wpt-commits: 9eb7edb448e51c8c3e024608484290f19f374415
wpt-pr: 23178
2020-04-30 19:03:32 +00:00
Oriol Brufau ac03d8feca Bug 1632230 [wpt PR 23175] - Sort CSS computed style properties in lexicographical order, again, a=testonly
Automatic update from web-platform-tests
Sort CSS computed style properties in lexicographical order, again

This is a follow-up of r760732, where I included logical properties when
iterating a computed style declaration. The problem was that I inserted
some of them at the wrong position, breaking the lexicographical order
achieved in r760690.

This time I add a test that checks that the order is right.

BUG=1072722,1072180

TEST=external/wpt/css/cssom/cssstyledeclaration-csstext.html
TEST=external/wpt/css/cssom/getComputedStyle-property-order.html

Change-Id: I3ea31024deed8b5a4c67a5a117c358cab6c9d7d4

--

wpt-commits: dbe025b0ce82a78a68bf63e7f657615378cbcb39
wpt-pr: 23175
2020-04-30 19:03:31 +00:00
Martin Robinson c1bebe6c49 Bug 1632106 [wpt PR 23166] - Add support for canceling CSS transitions, a=testonly
Automatic update from web-platform-tests
Add support for canceling CSS transitions

This change adds support for canceling CSS transitions when a property
is no longer transitionable or when an element becomes styled with
display:none. Support for canceling and replacing CSS transitions when
the end value changes is still pending. This change also takes advantage
of updating the constellation message to fix a bug where transition
events could be sent for closed pipelines.

Fixes #15079.

--

wpt-commits: 7c3ddf7343d1577cd5279fb132a17617feeebfe3
wpt-pr: 23166
2020-04-30 19:03:31 +00:00
moz-wptsync-bot 37caaca077 Bug 1630540 [wpt PR 22994] - Update wpt metadata, a=testonly
wpt-pr: 22994
wpt-type: metadata
2020-04-30 19:03:30 +00:00
Eriko Kurimoto b67977251f Bug 1630540 [wpt PR 22994] - DedicatedWorker: Refine WPTs to test parse error handling, a=testonly
Automatic update from web-platform-tests
DedicatedWorker: Refine WPTs to test parse error handling

This CL modifies web-platform-test for parse error handling in classic
and module dedicated workers.
This CL does followings:
1. Divide workers/modules/dedicated-worker-parse-error-failure.html into
the tests for classic workers and for module workers.
2. For module workers, check if module script is supported before
testing parse error handling.
3. Check the content of the dispatched event.

This change is based on WPTs for shared workers parse error handling.

Bug: 1071345
Change-Id: I738c89d5241a94df17092a3b106b5b795a26a7de

--

wpt-commits: f6f6077aab9fea53099084cd009e0701ca5dcfa7
wpt-pr: 22994
2020-04-30 19:03:30 +00:00
moz-wptsync-bot cd1ff4f771 Bug 1631356 [wpt PR 23105] - Update wpt metadata, a=testonly
wpt-pr: 23105
wpt-type: metadata
2020-04-30 19:03:29 +00:00
Hiroki Nakagawa 2c799c3062 Bug 1631356 [wpt PR 23105] - ServiceWorker: Fix timeout on client-navigate.https.html, a=testonly
Automatic update from web-platform-tests
ServiceWorker: Fix timeout on client-navigate.https.html

This CL fixes timeout on client-navigate.https.html, and removes unused
code in testharness.js.

This change is a follow-up for:
[1] https://github.com/web-platform-tests/wpt/pull/21162
[2] https://github.com/web-platform-tests/wpt/pull/22086

After the change [1], fetch_tests_from_workers() helper uses
ExtendableMessageEvent.source instead of MessageChannel to communicate
between a window and a service worker. This change works well for most
of cases, but fails some tests.

The fetch_tests_from_workers() helper takes a service worker object to
post a "connect" message to the worker, and then passes the worker
object to RemoteContext in testharness.js. RemoteContext adds an
onmessage event handler on self.navigator.serviceWorker. This works well
as long as the given worker object is associated with `self`. However,
these failing tests pass the worker object associated with the inner
frame to the helper. In this case, the helper uses an inner frame's
service worker object for postMessage(), while the helper waits on the
main frame's navigator.serviceWorker.onmessage. Consequently
event.source is the inner frame, and a reply from the service worker is
dispatched on the inner frame's navigator.serviceWorker.onmessage. This
results in timeout.

To fix this, this CL makes the main frame pass its own service worker
object instead of the inner frame's service worker object. Those
objects should be equal other than associated contexts, and this change
doesn't affect what the tests verify.

Bug: 1057682
Change-Id: I0f30f1fe9c54c3de1006276f3445c5e2b92ea5a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155760
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760974}

--

wpt-commits: 0a9ee5f5458c922aab15c25339db79e93df5c707
wpt-pr: 23105
2020-04-30 19:03:29 +00:00
moz-wptsync-bot f4153aeb1c Bug 1631923 [wpt PR 23151] - Update wpt metadata, a=testonly
wpt-pr: 23151
wpt-type: metadata
2020-04-30 19:03:28 +00:00
Navid Zolghadr 6378b77aad Bug 1631923 [wpt PR 23151] - Migrate pointerevents/touch-pointercancel.html to wpt, a=testonly
Automatic update from web-platform-tests
Migrate pointerevents/touch-pointercancel.html to wpt

pointerevents/touch-pointercancel.html test verifies
the touch and pointer events interaction in single
and multi touch point cases when scrolling happens or
not. The single touch point portion is already tested
as part of
wpt/pointerevents/pointerevent_pointercancel_touch.html

The two finger interaction is not very well specified
and is tested as part of
wpt/pointerevents/compat/pointerevent_touch-action_two-finger_interaction.html

and that only is missing the pointerid checks that
this CL adds as well.

Change-Id: I3ee27866dddc02cb87b1082b5a4fe2f9e8ba9220
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159577
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761123}

--

wpt-commits: eec9d65928b85f2ab8dc5252deb128d2246994af
wpt-pr: 23151
2020-04-30 19:03:28 +00:00
Stephen McGruer 43661e1c47 Bug 1630628 [wpt PR 23007] - Replace assert_precondition with assert_equals in domparsing/, a=testonly
Automatic update from web-platform-tests
Replace assert_precondition with assert_equals in domparsing/ (#23007)

assert_precondition is deprecated (see
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/assert_precondition_rename.md).
In this particular case, the assertion is actually checking for an
equality rather than an 'implements' phrase, so switch to assert_equals.
--

wpt-commits: e65087045387dd4ecb9d5c675062a6643e00c7ad
wpt-pr: 23007
2020-04-30 19:03:28 +00:00
Elly Fong-Jones e3873662f9 Bug 1633435 [wpt PR 23173] - Revert "[EventTiming] Add shadow DOM test for first input", a=testonly
Automatic update from web-platform-tests
Revert "[EventTiming] Add shadow DOM test for first input"

This reverts commit 9591b7074cacf1e8aeb9082dee2a4f46a171083f.

Reason for revert:
Failed blink_web_tests on webkit linux leak: https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20Leak/13490:

({"numberOfLiveContextLifecycleStateObservers":[2,5],"numberOfLiveDocuments":[1,2],"numberOfLiveNodes":[4,21],"numberOfLiveResourceFetchers":[1,2],"numberOfLiveResources":[0,4]})

Original change's description:
> [EventTiming] Add shadow DOM test for first input
>
> This CL tests event.target for first-input. The DOM elements do not have
> event listeners to show that event retargetting correctly retargets to
> the shadow host.
>
> Bug: 543598
> Change-Id: Ibd5a4a37a50f79b86d93a5c9c18c8ac7300ba723
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159622
> Reviewed-by: Steve Kobes <skobes@chromium.org>
> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#761417}

TBR=skobes@chromium.org,npm@chromium.org

Change-Id: I941e3f093e3d1fcba6662a54dec51b66690c9d70
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 543598
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2161125
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761446}

--

wpt-commits: b0e8930b6ed1b39a4bb9341a772b4efbc9ccb5f6
wpt-pr: 23173
2020-04-30 19:03:27 +00:00
Frédéric Wang a64e9c7516 Bug 1632190 [wpt PR 23171] - Add MathML tests for color/visibility of normal, large and stretchy mo., a=testonly
Automatic update from web-platform-tests
Add MathML tests for color/visibility of normal, large and stretchy mo. (#23171)

https://github.com/mathml-refresh/mathml/issues/57
--

wpt-commits: 4338d5203d020abe7249f34f93dc170c32c23dfa
wpt-pr: 23171
2020-04-30 19:03:27 +00:00
moz-wptsync-bot da54eddfd4 Bug 1632044 [wpt PR 23164] - Update wpt metadata, a=testonly
wpt-pr: 23164
wpt-type: metadata
2020-04-30 19:03:26 +00:00
Anne van Kesteren 850c40418b Bug 1632044 [wpt PR 23164] - XHR: align with Fetch's Content-Type stripping, a=testonly
Automatic update from web-platform-tests
XHR: align with Fetch's Content-Type stripping

Also modernize the code a tiny bit.

Closes #23156.

--

wpt-commits: 79311e3ce537612a80c21afc0013ee074d1fc5c1
wpt-pr: 23164
2020-04-30 19:03:26 +00:00
Anne van Kesteren 01dee87a5d Bug 1632195 [wpt PR 23172] - Wasm: ensure expected results are booleans, a=testonly
Automatic update from web-platform-tests
Wasm: ensure expected results are booleans

Follow-up to 6a1b15e5d699a00d58844b53e8c18d368169018d.

--

wpt-commits: 0d43c214401f06e0adfb8dc1afd1a15b52109e28
wpt-pr: 23172
2020-04-30 19:03:25 +00:00
moz-wptsync-bot a9f53bbfff Bug 1631967 [wpt PR 23155] - Update wpt metadata, a=testonly
wpt-pr: 23155
wpt-type: metadata
2020-04-30 19:03:25 +00:00
Nicolás Peña Moreno e9cf81099e Bug 1631967 [wpt PR 23155] - [EventTiming] Add shadow DOM test for first input, a=testonly
Automatic update from web-platform-tests
[EventTiming] Add shadow DOM test for first input

This CL tests event.target for first-input. The DOM elements do not have
event listeners to show that event retargetting correctly retargets to
the shadow host.

Bug: 543598
Change-Id: Ibd5a4a37a50f79b86d93a5c9c18c8ac7300ba723
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159622
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761417}

--

wpt-commits: 8fe6544d7211fe841ada747897674310973ee429
wpt-pr: 23155
2020-04-30 19:03:24 +00:00
autofoolip 781f641a83 Bug 1631652 [wpt PR 23127] - Update interfaces/DOM-Parsing.idl, a=testonly
Automatic update from web-platform-tests
Update interfaces/DOM-Parsing.idl (#23127)

Source: https://github.com/tidoust/reffy-reports/blob/66799cd/ed/idl/DOM-Parsing.idl
Build: https://travis-ci.org/tidoust/reffy-reports/builds/677501891
--

wpt-commits: 458f070cced571bb0f0739f79652f4788be9f923
wpt-pr: 23127
2020-04-30 19:03:24 +00:00
moz-wptsync-bot e8b19aa2fa Bug 1631817 [wpt PR 23142] - Update wpt metadata, a=testonly
wpt-pr: 23142
wpt-type: metadata
2020-04-30 19:03:23 +00:00
Anders Hartvoll Ruud 0e7dd32f62 Bug 1631817 [wpt PR 23142] - [@property] Ignore @property in shadow trees, a=testonly
Automatic update from web-platform-tests
[@property] Ignore @property in shadow trees

Bug: 973830, 978786
Change-Id: Iedf976e75098ecfa6158e4413f33bb3edba20381
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159222
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761385}

--

wpt-commits: ab523b11d595439e896c55fa32a99addc8557b0d
wpt-pr: 23142
2020-04-30 19:03:23 +00:00
Anders Hartvoll Ruud 1baf905fb0 Bug 1631961 [wpt PR 23154] - [@property] Support unregistering properties, a=testonly
Automatic update from web-platform-tests
[@property] Support unregistering properties

Having a declarative version of CSS.registerProperty means we must
effectively support unregistering properties as well: after all,
the stylesheet containing the @property can be removed with JS.

This CL implements that by clearing all declared registrations
from the registry when the active stylesheets change.

Bug: 973830, 978780
Change-Id: I5d5688176ecba75354a3b07750ebe47fb9c2949a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159216
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761359}

--

wpt-commits: 8e6a1cd4151d2a3387bfafebd54650c54a890695
wpt-pr: 23154
2020-04-30 19:03:22 +00:00
moz-wptsync-bot 3b272aaa02 Bug 1631989 [wpt PR 23159] - Update wpt metadata, a=testonly
wpt-pr: 23159
wpt-type: metadata
2020-04-30 19:03:22 +00:00
Anders Hartvoll Ruud 3fe27d14e9 Bug 1631989 [wpt PR 23159] - [@property] Add PropertyRegistry::Version, a=testonly
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
2020-04-30 19:03:21 +00:00
moz-wptsync-bot ddccae8e0f Bug 1631413 [wpt PR 23112] - Update wpt metadata, a=testonly
wpt-pr: 23112
wpt-type: metadata
2020-04-30 19:03:21 +00:00
Anne van Kesteren 8a7084cdba Bug 1631413 [wpt PR 23112] - Wasm: test SharedArrayBuffer-ness in another way, a=testonly
Automatic update from web-platform-tests
Wasm: test SharedArrayBuffer-ness in another way (#23112)

--

wpt-commits: 6a1b15e5d699a00d58844b53e8c18d368169018d
wpt-pr: 23112
2020-04-30 19:03:21 +00:00
Kunihiko Sakamoto 417f182200 Bug 1632031 [wpt PR 23161] - SignedExchange: Extend timeout of two tests, a=testonly
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
2020-04-30 19:03:20 +00:00
moz-wptsync-bot 0f3e60dcf6 Bug 1587902 [wpt PR 19632] - Update wpt metadata, a=testonly
wpt-pr: 19632
wpt-type: metadata
2020-04-30 19:03:20 +00:00
hiroshige-g e160f6cd8c Bug 1587902 [wpt PR 19632] - Scripts moved between documents, a=testonly
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
2020-04-30 19:03:19 +00:00
Alexander Cooper 5f7d8ce3b0 Bug 1631948 [wpt PR 23153] - Fix Webxr WPTs, a=testonly
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
2020-04-30 19:03:19 +00:00
moz-wptsync-bot 5807ae3505 Bug 1631731 [wpt PR 23134] - Update wpt metadata, a=testonly
wpt-pr: 23134
wpt-type: metadata
2020-04-30 19:03:18 +00:00
Anders Hartvoll Ruud 74b57bfc65 Bug 1631731 [wpt PR 23134] - [@property] Set status to 'test' and move tests to WPT, a=testonly
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
2020-04-30 19:03:18 +00:00
Robert Ma 085b58b0c1 Bug 1631100 [wpt PR 23075] - Set up py3-only tools/quic and its venv, a=testonly
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
2020-04-30 19:03:17 +00:00