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

Bug 1631356 [wpt PR 23105] - Update wpt metadata, a=testonly wpt-pr: 23105 wpt-type: metadata

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

Bug 1631923 [wpt PR 23151] - Update wpt metadata, a=testonly wpt-pr: 23151 wpt-type: metadata

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

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

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

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

Bug 1632044 [wpt PR 23164] - Update wpt metadata, a=testonly wpt-pr: 23164 wpt-type: metadata

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

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

Bug 1631967 [wpt PR 23155] - Update wpt metadata, a=testonly wpt-pr: 23155 wpt-type: metadata

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

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

Bug 1631817 [wpt PR 23142] - Update wpt metadata, a=testonly wpt-pr: 23142 wpt-type: metadata

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

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

Bug 1631989 [wpt PR 23159] - Update wpt metadata, a=testonly wpt-pr: 23159 wpt-type: metadata

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

Bug 1631413 [wpt PR 23112] - Update wpt metadata, a=testonly wpt-pr: 23112 wpt-type: metadata