searching for reviewer(testonly)
83710b53eef098a0b2a2184ab02e8bcd76a00ab9: Bug 1650184 - [wpt-sync] Update web-platform-tests to 145839c323ba1ec8b9737a3ed66924f6edd3624d, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Jul 2020 19:25:03 +0000 - rev 538687
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1650184 - [wpt-sync] Update web-platform-tests to 145839c323ba1ec8b9737a3ed66924f6edd3624d, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 145839c323ba1ec8b9737a3ed66924f6edd3624d wpt-type: landing
017d75a79fe32cbbdc4e8dc86eee7ffdfbb86e63: Bug 1646888 [wpt PR 24245] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Jul 2020 18:43:39 +0000 - rev 538686
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1646888 [wpt PR 24245] - Update wpt metadata, a=testonly wpt-pr: 24245 wpt-type: metadata
ae573dd9a49347bc3e15b91eaa36657546aa870f: Bug 1646888 [wpt PR 24245] - Update interfaces/webxr-ar-module.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 02 Jul 2020 19:24:39 +0000 - rev 538685
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1646888 [wpt PR 24245] - Update interfaces/webxr-ar-module.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webxr-ar-module.idl (#24245) Source: https://github.com/tidoust/reffy-reports/blob/9756a88/ed/idl/webxr-ar-module.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/699918508 -- wpt-commits: 145839c323ba1ec8b9737a3ed66924f6edd3624d wpt-pr: 24245
d61690dcdb29394684dc4750e89b6acd21208502: Bug 1648419 [wpt PR 24335] - Python 3: port tests in service-workers [part 2], a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:24:34 +0000 - rev 538684
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648419 [wpt PR 24335] - Python 3: port tests in service-workers [part 2], a=testonly Automatic update from web-platform-tests Python 3: port tests in service-workers [part 2] (#24335) -- wpt-commits: f2c264e640ea941f720b94a3e804a2676a51c7f8 wpt-pr: 24335
5c5df8c837e5c7dbca5a08cb2c78ae7b8b952733: Bug 1650064 [wpt PR 24423] - Python 3: port tests of range, stale-while-revalidate in fetch, a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:24:29 +0000 - rev 538683
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1650064 [wpt PR 24423] - Python 3: port tests of range, stale-while-revalidate in fetch, a=testonly Automatic update from web-platform-tests Python 3: port tests of range, stale-while-revalidate in fetch (#24423) * Python 3: port tests of range, stale-while-revalidate in fetch * Remove unnecessary prefix and use bytes type for content_range -- wpt-commits: b13c1d42b3aaf52a4e7b0b18795aeefb17a62eb6 wpt-pr: 24423
d56a1333e651227539772803a93d25bd6d80875e: Bug 1647715 [wpt PR 24311] - Implement CSPEE Blanket Enforcement logic out-of-blink, a=testonly
Antonio Sartori <antoniosartori@chromium.org> - Thu, 02 Jul 2020 19:24:24 +0000 - rev 538682
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1647715 [wpt PR 24311] - Implement CSPEE Blanket Enforcement logic out-of-blink, a=testonly Automatic update from web-platform-tests Implement CSPEE Blanket Enforcement logic out-of-blink This changes adds to the AncestorThrottle a check for the step "Does response allow blanket enforcement of policy from request" of Content Security Policy: Embedded Enforcement: https://w3c.github.io/webappsec-cspee/#origin-allowed Behind the flag This is one of the steps of moving CSPEE out-of-blink and is hidden under the flag network::features::kOutOfBlinkCSPEE. Change-Id: Id3092322134e055810d4006e63e6974ee64315be Bug: 1094909 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218019 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#784753} -- wpt-commits: 8a3698a69e785aefc5c83ea2e348fd3350bfa43a wpt-pr: 24311
0ccc7a3b5586ff4dbbe4588338a0b592464f8f52: Bug 1650035 [wpt PR 24421] - Move asserts inside the test, a=testonly
Philip Jägenstedt <philip@foolip.org> - Thu, 02 Jul 2020 19:24:14 +0000 - rev 538681
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1650035 [wpt PR 24421] - Move asserts inside the test, a=testonly Automatic update from web-platform-tests Move asserts inside the test (#24421) Failing one of these asserts would otherwise result in a harness error. -- wpt-commits: f5c167568d5f5c02ef9a3b3131c64f3a254c2296 wpt-pr: 24421
5d83e4eee60d5b9b02dc904d2a86c10d325997c1: Bug 1649113 [wpt PR 24380] - Test `browser`, `minimal-ui`, and `fullscreen` values of the `display` member, a=testonly
Christian Liebel <christian.liebel@thinktecture.com> - Thu, 02 Jul 2020 19:24:09 +0000 - rev 538680
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649113 [wpt PR 24380] - Test `browser`, `minimal-ui`, and `fullscreen` values of the `display` member, a=testonly Automatic update from web-platform-tests [appmanifest] add more display member tests (#24380) -- wpt-commits: aa28173104b557d7c0d4298944f73b5d0308ad74 wpt-pr: 24380
92b1908b3978c133de845c64dc5aebefe8624898: Bug 1649293 [wpt PR 24388] - Update bug references in docs and comments: s/891872/1098938/., a=testonly
Lukasz Anforowicz <lukasza@chromium.org> - Thu, 02 Jul 2020 19:24:04 +0000 - rev 538679
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649293 [wpt PR 24388] - Update bug references in docs and comments: s/891872/1098938/., a=testonly Automatic update from web-platform-tests Update bug references in docs and comments: s/891872/1098938/. Even though https://crbug.com/891872 is fixed (and blink::Platform::CreateDefaultURLLoaderFactory removed), |request_initiator_site_lock| might still be a base::nullopt in some URLLoaderFactory objects vended to renderer processes. Such remaining cases are tracked in https://crbug.com/1098938 - this CL updates bug references in docs and comments to match. Bug: 891872, 1098938 Change-Id: I64f21f2495514ba72bfcc3c39910151322b176eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274188 Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Steven Holte <holte@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#784738} -- wpt-commits: 3ecff280b727451096f3e3a8b0e9af301ec84263 wpt-pr: 24388
451caa350a6e56bb3e25510ab3ad7fbb5c5669b3: Bug 1649761 [wpt PR 24412] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Jul 2020 11:04:56 +0000 - rev 538678
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649761 [wpt PR 24412] - Update wpt metadata, a=testonly wpt-pr: 24412 wpt-type: metadata
4a20175eb069ce5e521becbdf9e864c5fbbf70f4: Bug 1649761 [wpt PR 24412] - Add a test to verify finding fragment id in non UTF8 document, a=testonly
Rob Buis <rbuis@igalia.com> - Thu, 02 Jul 2020 19:23:56 +0000 - rev 538677
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649761 [wpt PR 24412] - Add a test to verify finding fragment id in non UTF8 document, a=testonly Automatic update from web-platform-tests Add a test to verify finding fragment id in non UTF8 document (#24412) -- wpt-commits: 7e6dcb93c97da79840977f0f7b3aff6bf15da3eb wpt-pr: 24412
ebdd81093bc7e57bc0aa4b404e107a8e85515310: Bug 1649830 [wpt PR 24416] - [FragmentItem] Clear inline fragment index for positioned objects, a=testonly
Koji Ishii <kojii@chromium.org> - Thu, 02 Jul 2020 19:23:51 +0000 - rev 538676
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649830 [wpt PR 24416] - [FragmentItem] Clear inline fragment index for positioned objects, a=testonly Automatic update from web-platform-tests [FragmentItem] Clear inline fragment index for positioned objects When once laid out floating object is changed to a positioned object, it may have |FirstInlineFragmentItemIndex| set, but positioned objects should not have the index because they do not produce |NGFragmentIem|. This patch makes sure the index is cleared for positioned objects. Also this patch turns DCHECK in |NGInlineCursor::MoveTo| to NOTREACHED + return to avoid such case could result in crash. This is a regression in r784297 <crrev.com/c/2275373>, which started to index floating objects. Bug: 1101277 Change-Id: I21a75440c3aa77a8d66b1e002d05ff2b252e6b94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275820 Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#784685} -- wpt-commits: 99a09c73e7f1d7b19ec4be2eb8ce2d3bebf52245 wpt-pr: 24416
5a08b4fc2e240bab1dee46b9ffdbe36892dd7199: Bug 1649933 [wpt PR 24419] - Update interfaces/webauthn.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 02 Jul 2020 19:23:46 +0000 - rev 538675
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649933 [wpt PR 24419] - Update interfaces/webauthn.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webauthn.idl (#24419) Source: https://github.com/tidoust/reffy-reports/blob/3aeee91/ed/idl/webauthn.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/704148374 -- wpt-commits: dc9327cd43c5b07679de412e5ff29d7935b4ecdc wpt-pr: 24419
039a3de6cd28027d9ad37ce2bf36a5dd66f7a4b7: Bug 1649934 [wpt PR 24420] - Display type of ::first-line pseudo-elements, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 02 Jul 2020 19:23:42 +0000 - rev 538674
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649934 [wpt PR 24420] - Display type of ::first-line pseudo-elements, a=testonly Automatic update from web-platform-tests Display type of ::first-line pseudo-elements According to the spec, the display property should not be applied to ::first-line or ::first-letter pseudo-elements. https://www.w3.org/TR/css-display-3/#placement This has already been handled for ::first-letter, so this change similarly adjusts the display property style for ::first-line. I've tested the behavior in FireFox and legacy Edge, and this change aligns with the behavior in other browsers. Bug: 685925 Change-Id: Idaa299c90e20c69902491837b53e7988da7759c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2278321 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#784655} -- wpt-commits: 97361605eaf811be5120d97ddf807c735e9a8d22 wpt-pr: 24420
264d2200bb1c7d876ca9fcbf32c3c98f48bb9dbd: Bug 1649891 [wpt PR 24417] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Jul 2020 05:30:27 +0000 - rev 538673
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649891 [wpt PR 24417] - Update wpt metadata, a=testonly wpt-pr: 24417 wpt-type: metadata
a2bb24ae2670ab4106511109f92d78b150cd56dc: Bug 1649891 [wpt PR 24417] - Progress elements need reattach on appearance change., a=testonly
Rune Lillesveen <futhark@chromium.org> - Thu, 02 Jul 2020 19:23:34 +0000 - rev 538672
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649891 [wpt PR 24417] - Progress elements need reattach on appearance change., a=testonly Automatic update from web-platform-tests Progress elements need reattach on appearance change. Dynamic changes to appearance to/from auto/none did not work. Bug: 853558 Change-Id: I9486a0f3111555ba1975fe28cc58a54b2e20b71c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276260 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#784645} -- wpt-commits: 2677b2edb9d8c5563a496b50cc033e8842614dd9 wpt-pr: 24417
c2cb28a0af876dc1421748db23291461e098c3dc: Bug 1648620 [wpt PR 24349] - WebXR - anchors WPTs - update to account for test API changes, a=testonly
Piotr Bialecki <bialpio@chromium.org> - Thu, 02 Jul 2020 19:23:29 +0000 - rev 538671
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648620 [wpt PR 24349] - WebXR - anchors WPTs - update to account for test API changes, a=testonly Automatic update from web-platform-tests WebXR - anchors WPTs - update to account for test API changes WebXR Test API PR with changes to the API: https://github.com/immersive-web/webxr-test-api/pull/69 Change-Id: I9a9833e7850eb8b2c464161042a467b031208b5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2268578 Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#784593} -- wpt-commits: bbda80e3e9964567acedd8537f5318b40896ac85 wpt-pr: 24349
a9df0e55125ebac02d364609f8d85814c70d307b: Bug 1649338 [wpt PR 24391] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Jul 2020 21:30:28 +0000 - rev 538670
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649338 [wpt PR 24391] - Update wpt metadata, a=testonly wpt-pr: 24391 wpt-type: metadata
c68ef131de17d1bdd4495998b7ab03d2a8c3f030: Bug 1649338 [wpt PR 24391] - [AspectRatio] Add test for computing inline size with constrained block size, a=testonly
Christian Biesinger <cbiesinger@chromium.org> - Thu, 02 Jul 2020 19:23:21 +0000 - rev 538669
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649338 [wpt PR 24391] - [AspectRatio] Add test for computing inline size with constrained block size, a=testonly Automatic update from web-platform-tests [AspectRatio] Add test for computing inline size with constrained block size This tests the behavior as specced in https://github.com/w3c/csswg-drafts/issues/5257 R=ikilpatrick@chromium.org Bug: 1045668 Change-Id: I75b945a008b9039b751fc7de54da86cbf399a7ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274255 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#784523} -- wpt-commits: b363daeddf3374072306c4f9ccf919261489aa13 wpt-pr: 24391
baf48d6af38a15ffe3e3666f34e4f169a9fb8aad: Bug 1649745 [wpt PR 24410] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Jul 2020 17:51:30 +0000 - rev 538668
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649745 [wpt PR 24410] - Update wpt metadata, a=testonly wpt-pr: 24410 wpt-type: metadata
08f9c886a6bee71bf8116750b98b928032593dab: Bug 1649745 [wpt PR 24410] - Add iframe lazy load event semantics test, a=testonly
Dominic Farolino <dom@chromium.org> - Thu, 02 Jul 2020 19:23:13 +0000 - rev 538667
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649745 [wpt PR 24410] - Add iframe lazy load event semantics test, a=testonly Automatic update from web-platform-tests Add iframe lazy load event semantics test This CL adds WPTs asserting that in-viewport loading=lazy iframes do not block the outer window load event. The test accompanies the spec change made at: https://github.com/whatwg/html/pull/5579. R=sclittle@chromium.org Bug: 1101175 Change-Id: I5e337f6c87c8198e8e5bae5a32263698fb3daf28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2277384 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by: Scott Little <sclittle@chromium.org> Cr-Commit-Position: refs/heads/master@{#784381} -- wpt-commits: 54eb49dcb97c59910f8b6d9830d73ea11366b7e5 wpt-pr: 24410
a14958ef24e261fbb7f9e96ea75d82df7f6f53c8: Bug 1646485 [wpt PR 24208] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Jul 2020 12:29:59 +0000 - rev 538666
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1646485 [wpt PR 24208] - Update wpt metadata, a=testonly wpt-pr: 24208 wpt-type: metadata
f74b6f303c5284240c7dfcae7d6b5e7ddc3849df: Bug 1646485 [wpt PR 24208] - Add interfaces/is-input-pending.idl and test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Thu, 02 Jul 2020 19:23:01 +0000 - rev 538665
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1646485 [wpt PR 24208] - Add interfaces/is-input-pending.idl and test, a=testonly Automatic update from web-platform-tests Add interfaces/is-input-pending.idl and test (#24208) Closes https://github.com/web-platform-tests/wpt/pull/24205 -- wpt-commits: f1378425537a4f74895fad230f886b730fd051ad wpt-pr: 24208
9515cd5c760ab6c2c2aae73d95228208cd9cc27d: Bug 1648565 [wpt PR 24345] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Jul 2020 09:41:28 +0000 - rev 538664
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648565 [wpt PR 24345] - Update wpt metadata, a=testonly wpt-pr: 24345 wpt-type: metadata
0b8c1fa0c371f6116a063445de1140579d8ab65f: Bug 1648565 [wpt PR 24345] - Add interfaces/webhid.idl and test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Thu, 02 Jul 2020 19:22:51 +0000 - rev 538663
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648565 [wpt PR 24345] - Add interfaces/webhid.idl and test, a=testonly Automatic update from web-platform-tests Add interfaces/webhid.idl and test (#24345) Closes https://github.com/web-platform-tests/wpt/pull/24228 -- wpt-commits: b89d7ff93b5076d389404f2a062b83e73754307f wpt-pr: 24345
a120c0ab2fbb4fe578fbf78db9319bcbc04be8fb: Bug 1646050 [wpt PR 24167] - Python 3: Port tests in content-security-policy, a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:22:46 +0000 - rev 538662
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1646050 [wpt PR 24167] - Python 3: Port tests in content-security-policy, a=testonly Automatic update from web-platform-tests Python 3: Port tests in content-security-policy (#24167) -- wpt-commits: 423013266bec0213679b3fccab8e039bb3f68f0c wpt-pr: 24167
131fa8dd4b5030854d8fd11af4eb93f6438a0552: Bug 1646366 [wpt PR 24195] - Python 3: Port tests in fetch/corb, fetch/cross-origin-resource-polic…, a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:22:41 +0000 - rev 538661
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1646366 [wpt PR 24195] - Python 3: Port tests in fetch/corb, fetch/cross-origin-resource-polic…, a=testonly Automatic update from web-platform-tests Python 3: Port tests in fetch/corb, fetch/cross-origin-resource-policy and fetch/nosniff (#24195) -- wpt-commits: 71df9d040dfb23a381cab1a1d64ca380316c8a28 wpt-pr: 24195
105aeb6981fd8b32848a2bf25880ac3278762b9f: Bug 1649489 [wpt PR 24396] - [LayoutNG] Fix anonymous-block child-available-size., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Thu, 02 Jul 2020 19:22:36 +0000 - rev 538660
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649489 [wpt PR 24396] - [LayoutNG] Fix anonymous-block child-available-size., a=testonly Automatic update from web-platform-tests [LayoutNG] Fix anonymous-block child-available-size. The logic introduced for CalculateChildAvailableSize was designed to have the correct value for an element with: "<div style="position: relative; left: 50%; top: 50%;></div>" E.g. the percentage based left/top would resolve against the available size. However this broke text alignment within anonymous-blocks which require the child-available-size to be based on the actual inline-size. This patch uses the actual inline-size in the inline direction, but keeps the logic for block direction. This will mean that for postiion:relative calculations we'll use the Percentage inline-size, and Available block-size for resolving percentages. Bug: 1100203 Change-Id: I83c5281c5de9f9fd40f1bfed54e627dff5bb0600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274359 Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#784323} -- wpt-commits: 13b2394002dc74717d528a0f94c9a38d944fc578 wpt-pr: 24396
8fa872546a068ce2936367528c013142b8b33330: Bug 1649649 [wpt PR 24407] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Jul 2020 06:29:45 +0000 - rev 538659
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649649 [wpt PR 24407] - Update wpt metadata, a=testonly wpt-pr: 24407 wpt-type: metadata
732b9eaf1c512b0efa820dd6bff2fa225a96b9ed: Bug 1649649 [wpt PR 24407] - Augment iframe lazyload tests for srcdoc, a=testonly
Dominic Farolino <dom@chromium.org> - Thu, 02 Jul 2020 19:22:28 +0000 - rev 538658
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649649 [wpt PR 24407] - Augment iframe lazyload tests for srcdoc, a=testonly Automatic update from web-platform-tests Augment iframe lazyload tests for srcdoc This CL augments the existing iframe lazyload test for srcdoc lazyload support. Chrome currently does not implement this. The test accompanies the spec change made at: https://github.com/whatwg/html/pull/5579. R=sclittle@chromium.org Bug: 1101170 Change-Id: I5c5790c5d2eca3efbb01c5470e2267f2265858f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276624 Reviewed-by: Scott Little <sclittle@chromium.org> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#784331} -- wpt-commits: 36c3b7dbdcb6f955ef2d64aad14efb13c80e4c67 wpt-pr: 24407
6a07a54e62051efffc8c098464ed9799ad46d06c: Bug 1649550 [wpt PR 24399] - [FragmentItem] Include floats in associated LayoutObject, a=testonly
Koji Ishii <kojii@chromium.org> - Thu, 02 Jul 2020 19:22:23 +0000 - rev 538657
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649550 [wpt PR 24399] - [FragmentItem] Include floats in associated LayoutObject, a=testonly Automatic update from web-platform-tests [FragmentItem] Include floats in associated LayoutObject This patch changes to associate floating |LayoutObject|s to |NGFragmentItem| using |FirstInlineFragmentItemIndex|. The index is used for many purposes, but one of them is to mark destroyed or moved |LayoutObject| in |NGFragmentItem|. Because floating objects are stored in |NGFragmentItem|, they need to be indexed to mark correctly. Also changes |LayoutBlockFlow:: SetShouldDoFullPaintInvalidationForFirstLine| to skip items for destroyed or moved |LayoutObject| because it may be called on dirty tree. Bug: 1100900 Change-Id: If35bf2c77b9a46a9ba598e6785926f6b0e1c5455 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2275373 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#784297} -- wpt-commits: e5fea0ad9e468165aba081d71880ec2b67832df6 wpt-pr: 24399
2ed219496dcf99f5f952c6108c62e9161c3c388a: Bug 1649619 [wpt PR 24402] - [PaintTiming] Let videos trigger FCP, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Thu, 02 Jul 2020 19:22:18 +0000 - rev 538656
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649619 [wpt PR 24402] - [PaintTiming] Let videos trigger FCP, a=testonly Automatic update from web-platform-tests [PaintTiming] Let videos trigger FCP This CL adds a call to SetImagePainted() so that FCP fires when there we paint a video. Bug: 1071450 Change-Id: I9590517fd3355226096fd62079a3a4aa6eb50735 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276244 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#784189} -- wpt-commits: 17f0e364e3584535436669a490887e723f3f61e6 wpt-pr: 24402
b519a60a16ea4a2063cc9bd55808e35d90cfcb6d: Bug 1649586 [wpt PR 24401] - Named pages should only have an effect when paginated., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 02 Jul 2020 19:22:11 +0000 - rev 538655
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649586 [wpt PR 24401] - Named pages should only have an effect when paginated., a=testonly Automatic update from web-platform-tests Named pages should only have an effect when paginated. Need to check if page breaks are applicable before applying them. Bug: 1100308, 1053768 Change-Id: I987bf4ce42f7d0f5128cb01c30824214d9c12ea8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2276432 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#784139} -- wpt-commits: 046463806888ea0f241f4df19c1bcc23b3d8e50c wpt-pr: 24401
f0b4bc5edd96e22b8b95ae1c7422f55b35a61c48: Bug 1648529 [wpt PR 24344] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 30 Jun 2020 22:49:14 +0000 - rev 538654
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648529 [wpt PR 24344] - Update wpt metadata, a=testonly wpt-pr: 24344 wpt-type: metadata
7dee3dfa714f190e4d62865062cca1ef7e5249d3: Bug 1648529 [wpt PR 24344] - Accept Permissions-Policy header, a=testonly
Charlie Hu <chenleihu@google.com> - Thu, 02 Jul 2020 19:22:03 +0000 - rev 538653
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648529 [wpt PR 24344] - Accept Permissions-Policy header, a=testonly Automatic update from web-platform-tests Accept Permissions-Policy header This CL does the necessary plumbing so that permissions policy header can be properly parsed and merged with existing init procedure of feature policy. A few wpt tests are added to verify that the plumbing is working as expected. Change-Id: I64b956f55fc36e372c23d6f1df92af54e268d92c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246981 Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Charlie Hu <chenleihu@google.com> Cr-Commit-Position: refs/heads/master@{#784064} -- wpt-commits: af272845618c79b04d7fdcf9687e9ab9b543b6d7 wpt-pr: 24344
2c9d17a107a82cee9e7ecd7d437c8b6df855baac: Bug 1649536 [wpt PR 24398] - Fix clip state of synthetic effect for non-backdrop effects, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Thu, 02 Jul 2020 19:21:58 +0000 - rev 538652
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649536 [wpt PR 24398] - Fix clip state of synthetic effect for non-backdrop effects, a=testonly Automatic update from web-platform-tests Fix clip state of synthetic effect for non-backdrop effects This fixes a regression caused by crrev.com/c/2183198. We should move the effect's clip to the outer synthetic effects for backdrop effects only. For non-backdrop effect we don't move effect up into the synthetic effect and can share the synthetic effect with other effects, so we should not move up the clip. Bug: 1099234 Change-Id: I5dbd63f7c94717e42572342371df6de8fe89308e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2272122 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#784097} -- wpt-commits: 716a3224e9a754234c2fc1166ca6757154a445c0 wpt-pr: 24398
89107c9a6027517b7368c43403136cd1caf92f8e: Bug 1645485 [wpt PR 24134] - client hints: Rework how persistent settings are communicated to renderer, a=testonly
Maks Orlovich <morlovich@chromium.org> - Thu, 02 Jul 2020 19:21:54 +0000 - rev 538651
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1645485 [wpt PR 24134] - client hints: Rework how persistent settings are communicated to renderer, a=testonly Automatic update from web-platform-tests client hints: Rework how persistent settings are communicated to renderer Before this CL, the entire settings map was sent to the renderer, it then parsed accept-ch, and sent IPCs to the browser to persist settings. This has following downsides: 1) client-hint settings map can leak history to render (I don't know if there are other sources of that, probably, so maybe not such a big deal) 2) If this becomes popular, map size would be a performance risk 3) This requires trusting renderer to update client hint settings. Instead, this uses existing network service hook to parse accept-ch (which was needed for navigation redirects), and the browser persists the results and sends the relevant client hint configuration to the renderer with CommitParams. The IPC for renderer to write config is therefore removed. This required teaching the browser code to behave more consistently with some flags (lang, accept-ch-lifetime support). Change-Id: I421b3c07d4644e179a0f6a26088e44c55f68f7d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2081628 Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Camille Lamy <clamy@chromium.org> Reviewed-by: Tarun Bansal <tbansal@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#784031} -- wpt-commits: db1baf1ad1b70d9343284bab7d55dd4f7ba1e07b wpt-pr: 24134
2a2ddae7c42339fe22773f78510e4234df2c8971: Bug 1649434 [wpt PR 24394] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 30 Jun 2020 17:15:32 +0000 - rev 538650
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649434 [wpt PR 24394] - Update wpt metadata, a=testonly wpt-pr: 24394 wpt-type: metadata
c92980fea3dc2946d045f58d37c3e11ad9c80481: Bug 1649434 [wpt PR 24394] - Partially revert "Add another https port (#24016)", a=testonly
Stephen McGruer <smcgruer@chromium.org> - Thu, 02 Jul 2020 19:21:35 +0000 - rev 538649
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649434 [wpt PR 24394] - Partially revert "Add another https port (#24016)", a=testonly Automatic update from web-platform-tests Partially revert "Add another https port (#24016)" (#24394) This reverts the change to common/get-host-info.sub.js in commit 95cdf1f. Adding another HTTPS port broke there broke the Chromium WPT Importer (as the pinned tooling failed to sub common/get-host-info.sub.js due to indexing out of bounds). -- wpt-commits: c9d349e49b3140029e4682761d5af5189ae75138 wpt-pr: 24394
d0710fad8a934b4cf8356d217cb2ffa15b0e5ead: Bug 1649310 [wpt PR 24390] - [WPT] Fix external/wpt/css/css-backgrounds/border-image-shorthand-001.htm, a=testonly
Stephen Chenney <schenney@chromium.org> - Thu, 02 Jul 2020 19:21:30 +0000 - rev 538648
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649310 [wpt PR 24390] - [WPT] Fix external/wpt/css/css-backgrounds/border-image-shorthand-001.htm, a=testonly Automatic update from web-platform-tests [WPT] Fix external/wpt/css/css-backgrounds/border-image-shorthand-001.htm The test file and it's reference differed by having a "." inside or outside the <strong>. Fix it. TBR: pdr@chromium.org Bug: 1099732 Change-Id: Ia70fc06fa216bd5494187f18be27e46fa9e1dd36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274786 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#783938} -- wpt-commits: 7fbf0a9b035b850016885c4b27d267265de615f6 wpt-pr: 24390
a0fdfd92c90a1c2c2ef5c5ef63717c312948590e: Bug 1648429 [wpt PR 24338] - Python 3: port tests in service-workers [part 5], a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:21:25 +0000 - rev 538647
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648429 [wpt PR 24338] - Python 3: port tests in service-workers [part 5], a=testonly Automatic update from web-platform-tests Python 3: port tests in service-workers [part 5] (#24338) Use random.random() instead of time.clock() for script updates -- wpt-commits: a9e30a86cdcc6121a23512ea9178f80fba8fd233 wpt-pr: 24338
ef36ffe68a755682525dd2f7b0878d963e35fb73: Bug 1648426 [wpt PR 24337] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 30 Jun 2020 13:43:32 +0000 - rev 538646
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648426 [wpt PR 24337] - Update wpt metadata, a=testonly wpt-pr: 24337 wpt-type: metadata
223cd90282cac0ba38f87e58978ea212fca4fd65: Bug 1648426 [wpt PR 24337] - Python 3: port tests in service-workers [part 4], a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:21:17 +0000 - rev 538645
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648426 [wpt PR 24337] - Python 3: port tests in service-workers [part 4], a=testonly Automatic update from web-platform-tests Python 3: port tests in service-workers [part 4] (#24337) -- wpt-commits: a3d97e7272302008c34864b3122e6d31b35faa6c wpt-pr: 24337
322aa5bf77a89a05577c9d14df9f2fcefbb70510: Bug 1649392 [wpt PR 24392] - Fix wpt/html/coep/require-corp-about-{blank,srcdoc}.html, a=testonly
Yutaka Hirano <yhirano@chromium.org> - Thu, 02 Jul 2020 19:21:12 +0000 - rev 538644
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649392 [wpt PR 24392] - Fix wpt/html/coep/require-corp-about-{blank,srcdoc}.html, a=testonly Automatic update from web-platform-tests Fix wpt/html/coep/require-corp-about-{blank,srcdoc}.html - platform/mac-mac10.13/.../require-corp-about-blank-expected.txt is redundant - it's same as the base expectation. - platform/mac-mac10.14/.../require-corp-about-blank-expected.txt is wrong - the test always fails on the platform (and the failures are suppressed by TestExpectations). - wpt/html/coep/require-corp-about-blank.html always fails because COEP is only effective on secure contexts (https://github.com/whatwg/html/issues/4930). Rename it to wpt/html/coep/require-corp-about-blank.https.html - wpt/html/coep/require-corp-about-srcdoc.html always fails because COEP is only effective on secure contexts (https://github.com/whatwg/html/issues/4930). Rename it to wpt/html/coep/require-corp-about-srcdoc.https.html - Remove redundant TestExpectations entries. Bug: 1086065, 626703 Change-Id: I5573dd4446f482acdde828404e0a88893897ce09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274133 Auto-Submit: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#783875} -- wpt-commits: f911e6744606f48835f3296fab56e40d8185121c wpt-pr: 24392
23c288a46f2e5c55f7e720dcced9778a5e828f42: Bug 1649081 [wpt PR 24378] - Test `orientation` member, a=testonly
Christian Liebel <christian.liebel@thinktecture.com> - Thu, 02 Jul 2020 19:21:07 +0000 - rev 538643
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649081 [wpt PR 24378] - Test `orientation` member, a=testonly Automatic update from web-platform-tests [appmanifest] Test `orientation` member (#24378) * [appmanifest] Add orientation member test * [appmanifest] add portrait orientation test -- wpt-commits: 1cb9daef513ee0c7e82a6689a6248946d0c580c0 wpt-pr: 24378
875493d2397f961cb292d66302f332b51736f968: Bug 1649257 [wpt PR 24386] - Indexed DB: Use correct range upper limit for index iteration, a=testonly
Joshua Bell <jsbell@chromium.org> - Thu, 02 Jul 2020 19:21:02 +0000 - rev 538642
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649257 [wpt PR 24386] - Indexed DB: Use correct range upper limit for index iteration, a=testonly Automatic update from web-platform-tests Indexed DB: Use correct range upper limit for index iteration When iterating a forwards, comparisons are done between each record found and the range's bound to know when to stop. There's an special case for reverse cursors where a starting key is needed at the upper end of the range, so the uppermost key in the range is looked up as the starting cursor position. The code to do this for indexes was not guarded by a check for the cursor direction, though. This was harmless for most forward iterations as the uppermost actual key would match the upper bound anyway. But when iterating a cursor over a range in an index, records can change their index keys and thus appear again in the iteration. This would lead to the cursor stopping at what was no longer the actual uppermost key in the range, missing records in the iteration. Add the missing check, and a WPT to verify this behavior. (The code dates back to before 2013, so this is not a recent regression.) Bug: 1091731 Change-Id: I23336ba03d31607607d496fc7e18c28bcf644cf0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274085 Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#783792} -- wpt-commits: 93caf8cf824c75e47a68af9d3000e297139c4974 wpt-pr: 24386
ae2094113e1b9430eae2c5b6a4d56e85f9a112a2: Bug 1649252 [wpt PR 24384] - Setting innerHTML in a template element in an inactive document should not crash., a=testonly
Nate Chapin <japhet@chromium.org> - Thu, 02 Jul 2020 19:20:57 +0000 - rev 538641
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1649252 [wpt PR 24384] - Setting innerHTML in a template element in an inactive document should not crash., a=testonly Automatic update from web-platform-tests Setting innerHTML in a template element in an inactive document should not crash. Bug: 1100176 Test: html/semantics/scripting-1/the-template-element/template-element/template-set-inner-html-in-inactive-document-crash.html Change-Id: I1d2ad61aead0d8f14952ae9b8e49d855d773e86f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2273798 Auto-Submit: Nate Chapin <japhet@chromium.org> Reviewed-by: Mason Freed <masonfreed@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#783693} -- wpt-commits: 825a7c1a712e0911116031b5e5dcf382d8f50adb wpt-pr: 24384
d056a488a00b78686304a36629cb7cc121ed9b72: Bug 1641952 [wpt PR 23860] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 30 Jun 2020 00:03:30 +0000 - rev 538640
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1641952 [wpt PR 23860] - Update wpt metadata, a=testonly wpt-pr: 23860 wpt-type: metadata
c6f861b3f81380653b1c2e8c15f5b8923cec5417: Bug 1641952 [wpt PR 23860] - Fix calculation of before change style for CSS transitions, a=testonly
Kevin Ellis <kevers@chromium.org> - Thu, 02 Jul 2020 19:20:47 +0000 - rev 538639
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1641952 [wpt PR 23860] - Fix calculation of before change style for CSS transitions, a=testonly Automatic update from web-platform-tests Fix calculation of before change style for CSS transitions This patch performs a lazy calculation of the before change style once it has been determined that a transition is being retargeted. In doing so, the current position is correctly updated to reflect changes made via the web-animation API. The path also addresses a bug in the calculation of current time, in the case of a paused or play-pending animation. Bug: 1082401, 888661, 547609 Change-Id: I4b76879d840b482da8ebf23c1aad41b881fafce8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220263 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/master@{#783675} -- wpt-commits: ebe69e97a1ea77b2eb30d7b40ffef2d67455a805 wpt-pr: 23860
60176a9eff2185bc9bb2625fbcb46132f7b751db: Bug 1648431 [wpt PR 24339] - Python 3: port tests in service-workers [part 6], a=testonly
ziransun <zsun@igalia.com> - Thu, 02 Jul 2020 19:20:38 +0000 - rev 538638
Push 37566 by ccoroiu@mozilla.com at Fri, 03 Jul 2020 15:35:32 +0000
Bug 1648431 [wpt PR 24339] - Python 3: port tests in service-workers [part 6], a=testonly Automatic update from web-platform-tests Python 3: port tests in service-workers [part 6] (#24339) -- wpt-commits: 5a9b76d3c380269ce95f11072923738ca09f5d2f wpt-pr: 24339