searching for reviewer(testonly)
5dedfa40a55fc4c3265fd036f5c9d89b5164db41: Bug 1725822 - [wpt-sync] Update web-platform-tests to 0bc996384524028f8608c311d35ee7ebdf29afca, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 14 Aug 2021 21:16:24 +0000 - rev 589304
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725822 - [wpt-sync] Update web-platform-tests to 0bc996384524028f8608c311d35ee7ebdf29afca, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 0bc996384524028f8608c311d35ee7ebdf29afca wpt-type: landing
f0f51a5e7551daac03af5d77c5db87d7d1144386: Bug 1725804 [wpt PR 30032] - Remove non-invertible-transform-animation.html, a=testonly
Philip Rogers <pdr@chromium.org> - Sat, 14 Aug 2021 21:16:00 +0000 - rev 589303
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725804 [wpt PR 30032] - Remove non-invertible-transform-animation.html, a=testonly Automatic update from web-platform-tests Remove non-invertible-transform-animation.html The test added in https://crrev.com/911926 is failing on Safari: https://staging.wpt.fyi/results/css/css-animations/non-invertible-transform-animation.html This test only covered the behavior change in https://crrev.com/911926 when run manually because any runs of the lifecycle, such as the raf run at the end of the test, would hide the bug. The test was re-written using web animations which should pass reliably on Safari, but that approach hides the original bug when running the test manually. Because the WPT test is of minimal value, and the behavior change is tested via a unit test, this patch just removes the test. Bug: 1227011 Change-Id: I08f02d1c6e8f74eaddd036ed4cc479d9b47255d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3095427 Commit-Queue: Philip Rogers <pdr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#912002} -- wpt-commits: 0bc996384524028f8608c311d35ee7ebdf29afca wpt-pr: 30032
00872597d0741e64b398fdd565a040b3a71d362c: Bug 1725132 [wpt PR 29986] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 14 Aug 2021 01:03:39 +0000 - rev 589302
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725132 [wpt PR 29986] - Update wpt metadata, a=testonly wpt-pr: 29986 wpt-type: metadata
827a06fd047fe627675afe73b6d17c2f3fc0a87f: Bug 1725132 [wpt PR 29986] - Rely on the CSS serializer for CanvasTextDrawingStyles.font, a=testonly
Frédéric Wang <fwang@igalia.com> - Sat, 14 Aug 2021 21:15:50 +0000 - rev 589301
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725132 [wpt PR 29986] - Rely on the CSS serializer for CanvasTextDrawingStyles.font, a=testonly Automatic update from web-platform-tests Rely on the CSS serializer for CanvasTextDrawingStyles.font According to the canvas specification [1]: "On getting, the font attribute must return the serialized form of the current font of the context (with no 'line-height' component)." This patch changes the implementations of CanvasRenderingContext2D OffscreenCanvasRenderingContext2D so that the font-family part is serialized via the CSS serializer [2] [3] [4]. This reduces code duplication and makes things more consistent in preparation for [5]. In particular, this changes the following: - Font family names are always quoted when necessary (e.g. if they contain a quote or a comma), while this used to only be done when they contain an ASCII space U+0020. - The "-webkit" prefix prepended to some generic font families names (namely "cursive", "fantasy", "monospace", "sans-serif" and "serif") is removed ; while this used to be done for all font family names with a "-webkit" prefix. - Various character substitutions from [3] are performed, while no no such substitutions used to happen. One noticeable edge case is the escaping of double quote and backslash characters. The new serialization behavior aligns with Firefox. This is a considered a minor bug fix that "does not affect web API behavior to the point that developers need to be aware of it" and so is exempt from an I2S [6]. [1] https://html.spec.whatwg.org/multipage/canvas.html#text-styles [2] https://drafts.csswg.org/cssom/#serialize-a-comma-separated-list [3] https://drafts.csswg.org/cssom/#serialize-a-string [4] https://drafts.csswg.org/cssom/#serialize-an-identifier [5] https://bugs.chromium.org/p/chromium/issues/detail?id=1065468 [6] https://www.chromium.org/blink/launching-features Bug: 1065468 Change-Id: I7003705af8010cbb9723ee8d0a6c39e083f9eef7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3086444 Reviewed-by: Yi Xu <yiyix@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#911930} -- wpt-commits: 6fc4f27b2befb9e5cb8256fd41617dedd16d691a wpt-pr: 29986
a355b31e7e6ae5224670c9faf20b4f2080b3f45e: Bug 1725720 [wpt PR 30026] - [CompositeAfterPaint] Paint content under animating non-invertible xform, a=testonly
Philip Rogers <pdr@chromium.org> - Sat, 14 Aug 2021 21:15:42 +0000 - rev 589300
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725720 [wpt PR 30026] - [CompositeAfterPaint] Paint content under animating non-invertible xform, a=testonly Automatic update from web-platform-tests [CompositeAfterPaint] Paint content under animating non-invertible xform Before this patch, painting of content under non-invertible transforms was skipped in two places. This is problematic because a composited transform animation may become invertible later, but the compositor will not have content to show. This patch causes this content to paint. Another approach would be to not composite these animations, but the composited animation system already needs to handle non-invertible transforms (e.g., when animating scale(1) to scale(-1)) so these are compositable. Bug: 1227011 Change-Id: Idd41abef0919404e40473117064e6ffe221511ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3093707 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#911926} -- wpt-commits: dd7717aa14d7948715053416e0c048087ee7422f wpt-pr: 30026
61dcf8697495dd55b190a0cc92441e41c0acd8e7: Bug 1725695 [wpt PR 30023] - Fix some NotAllowedError --> SecurityError cases for PaymentRequest.show(), a=testonly
Stephen McGruer <smcgruer@chromium.org> - Sat, 14 Aug 2021 21:15:36 +0000 - rev 589299
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725695 [wpt PR 30023] - Fix some NotAllowedError --> SecurityError cases for PaymentRequest.show(), a=testonly Automatic update from web-platform-tests Fix some NotAllowedError --> SecurityError cases for PaymentRequest.show() (#30023) See https://github.com/w3c/payment-request/pull/961 -- wpt-commits: ee2d179bcea6e4a697e89a99a245e4571bd65097 wpt-pr: 30023
2e78c4132f2ba636c6504bf108eeed5f6caa5f0b: Bug 1725717 [wpt PR 30024] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Aug 2021 22:38:57 +0000 - rev 589298
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725717 [wpt PR 30024] - Update wpt metadata, a=testonly wpt-pr: 30024 wpt-type: metadata
2fd1f8004ea4b74ffe688a7f5f6813189192effe: Bug 1725717 [wpt PR 30024] - Add test for display: contents top layer handling, a=testonly
Tim Nguyen <ntim@apple.com> - Sat, 14 Aug 2021 21:15:25 +0000 - rev 589297
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725717 [wpt PR 30024] - Add test for display: contents top layer handling, a=testonly Automatic update from web-platform-tests Add test for display: contents top layer handling -- wpt-commits: e26769deba6c269b95be254b45bd14672a8eeb85 wpt-pr: 30024
4fe34aae75fd568ea675a4af971ef1b8b8654cea: Bug 1725497 [wpt PR 30014] - Add failing displaylocking+shadowdom crash tests, a=testonly
Joey Arhar <jarhar@chromium.org> - Sat, 14 Aug 2021 21:15:19 +0000 - rev 589296
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725497 [wpt PR 30014] - Add failing displaylocking+shadowdom crash tests, a=testonly Automatic update from web-platform-tests Add failing displaylocking+shadowdom crash tests These crashing tests were uncovered by clusterfuzz after I landed a patch to use content-visibility in <details>. It turned out that all of them could also reproduce the crash without the use of <details>, so here they are. Bug: 1236774 Change-Id: Ib44f6f8167929c90d4b78c6e153ad645767e1b58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3072277 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/master@{#911804} -- wpt-commits: 311020865156d2c6c5e4bbf159d7a82644b56509 wpt-pr: 30014
6388d5685b02c8f29920ab4f82bbf3d8f10a5026: Bug 1725653 - [wpt-sync] Update web-platform-tests to 37d215c69e495f287cc96902b47af64d21922305, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Aug 2021 15:33:30 +0000 - rev 589284
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725653 - [wpt-sync] Update web-platform-tests to 37d215c69e495f287cc96902b47af64d21922305, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 37d215c69e495f287cc96902b47af64d21922305 wpt-type: landing
eb660ba04e6066a0b09315b7ba918b4a85631cbb: Bug 1724876 [wpt PR 29967] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Aug 2021 13:48:11 +0000 - rev 589283
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724876 [wpt PR 29967] - Update wpt metadata, a=testonly wpt-pr: 29967 wpt-type: metadata
a9a66c0c1cd9e6f87698beeb11dd56354b11287b: Bug 1724876 [wpt PR 29967] - NativeIO: Add test for 0-length buffers, a=testonly
Richard Stotz <rstz@chromium.org> - Fri, 13 Aug 2021 15:30:33 +0000 - rev 589282
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724876 [wpt PR 29967] - NativeIO: Add test for 0-length buffers, a=testonly Automatic update from web-platform-tests NativeIO: Add test for 0-length buffers This CL adds a regression test to confirm that reading and writing do not fail on buffers of small length (0 - 3 bytes). Bug: 1237441 Change-Id: Iebad8d50b5423ebd68715bb54ce6dd0cd8c0aebb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3084742 Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Commit-Queue: Richard Stotz <rstz@chromium.org> Cr-Commit-Position: refs/heads/master@{#911709} -- wpt-commits: 37d215c69e495f287cc96902b47af64d21922305 wpt-pr: 29967
7d3b4f1b64bebfbfc0a3eb7909047c56069e6c6b: Bug 1724328 [wpt PR 29924] - Fix some shadow root tests, a=testonly
Jesus David García Gomez <1581288+sarvaje@users.noreply.github.com> - Fri, 13 Aug 2021 15:30:25 +0000 - rev 589281
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724328 [wpt PR 29924] - Fix some shadow root tests, a=testonly Automatic update from web-platform-tests Fix some shadow root tests (#29924) -- wpt-commits: db065869e8ff859e7d297b04b21115a9669da745 wpt-pr: 29924
34d48ab3f222f4b4557fca420446bff6641dc246: Bug 1694144 [wpt PR 29996] - [Gecko Bug 1694144] [wdspec] Split fixture module for WebDriver HTTP and BiDi., a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Aug 2021 15:29:31 +0000 - rev 589280
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1694144 [wpt PR 29996] - [Gecko Bug 1694144] [wdspec] Split fixture module for WebDriver HTTP and BiDi., a=testonly Automatic update from web-platform-tests [wdspec] Split fixture module for WebDriver HTTP and BiDi. Differential Revision: https://phabricator.services.mozilla.com/D122336 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1694144 gecko-commit: 118ad1445b60ec5624ef4f5a125fc9716d5abe40 gecko-reviewers: webdriver-reviewers, jgraham -- [wdspec] Add BiDi error classes to BiDi client. Differential Revision: https://phabricator.services.mozilla.com/D122337 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1694144 gecko-commit: c3cf28582710c2b5213a9a7dfd64283de664a675 gecko-reviewers: webdriver-reviewers, jgraham, jdescottes -- [wdspec] Add basic tests for "session.subscribe". Differential Revision: https://phabricator.services.mozilla.com/D122019 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1694144 gecko-commit: 34b56695cd5cae44500a1375d93eab057e3e91e0 gecko-reviewers: jgraham, webdriver-reviewers, jdescottes -- Fix flake8 and mypy linting errors -- wpt-commits: e288241ed009016eea75b3fe7670084137303029, 62521361ddb10cabddb4dcb7fa4f8b9adfb613ef, e1fd65132084d5677ded23086db3ebba97fdc013, d36b21efca19588e2707537f4a16cc7e3c91b05d wpt-pr: 29996
7d74f1991037daf3c7374bfb25ac88162e7d162f: Bug 1725522 [wpt PR 30017] - Fix several var() tests, a=testonly
Tab Atkins Jr <jackalmage@gmail.com> - Fri, 13 Aug 2021 14:32:31 +0000 - rev 589279
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725522 [wpt PR 30017] - Fix several var() tests, a=testonly Automatic update from web-platform-tests Fix several var() tests (#30017) -- wpt-commits: dfd2e8569778e2a8409d47b529bd062f7ce862b5 wpt-pr: 30017
2c2887ab96302250b54821a9e8304f9ce4b431ac: Bug 1725319 [wpt PR 30006] - Update show() test to match WebKit's behavior, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Fri, 13 Aug 2021 14:32:23 +0000 - rev 589278
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725319 [wpt PR 30006] - Update show() test to match WebKit's behavior, a=testonly Automatic update from web-platform-tests Update PR.show() test to match WebKit's behavior (#30006) -- wpt-commits: 661016a13f10f7e3566cf000718571ff815825eb wpt-pr: 30006
a565040bfbaa760509ed8e4a29453dc6c661d8ca: Bug 1725287 [wpt PR 30002] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 13 Aug 2021 02:25:49 +0000 - rev 589277
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725287 [wpt PR 30002] - Update wpt metadata, a=testonly wpt-pr: 30002 wpt-type: metadata
f4956920a8c6a7422098c956c82ca3c0c5f6e6fb: Bug 1725287 [wpt PR 30002] - Highlight API: Invalidate markers' nodes in prepaint phase, a=testonly
Fernando Fiori <ffiori@microsoft.com> - Fri, 13 Aug 2021 14:31:55 +0000 - rev 589276
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725287 [wpt PR 30002] - Highlight API: Invalidate markers' nodes in prepaint phase, a=testonly Automatic update from web-platform-tests Highlight API: Invalidate markers' nodes in prepaint phase Move HighlightRegistry::ValidateHighlightMarkers calls to prepaint phase so the nodes affected by the markers added/removed are invalidated and then repainted in the paint phase of this lifecycle. Also make tests wait until callback is executed. Bug: 1238845 Change-Id: I998af8632ba21c7c504c99290a3424be7537c569 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3088068 Reviewed-by: Stefan Zager <szager@chromium.org> Reviewed-by: Dan Clark <daniec@microsoft.com> Commit-Queue: Fernando Fiori <ffiori@microsoft.com> Cr-Commit-Position: refs/heads/master@{#911572} -- wpt-commits: 071d76fd176f11bc41afba153c2e1c0f8bec4028 wpt-pr: 30002
015b82300a5f1e9ee66c02f96329064bad550d55: Bug 1724529 [wpt PR 29935] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Aug 2021 20:52:59 +0000 - rev 589275
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724529 [wpt PR 29935] - Update wpt metadata, a=testonly wpt-pr: 29935 wpt-type: metadata
47c8ab4746bdf1aac4b27f934cd319dd4d09a8e6: Bug 1724529 [wpt PR 29935] - Support multiple calls to respondWith() for a single AppHistoryNavigateEvent, a=testonly
Nate Chapin <japhet@chromium.org> - Fri, 13 Aug 2021 14:31:41 +0000 - rev 589274
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724529 [wpt PR 29935] - Support multiple calls to respondWith() for a single AppHistoryNavigateEvent, a=testonly Automatic update from web-platform-tests Support multiple calls to respondWith() for a single AppHistoryNavigateEvent Fixed: 1221280 Change-Id: I4d3b2d9baf905da2b4f422f7e2a35a0f92e37c6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3077796 Commit-Queue: Domenic Denicola <domenic@chromium.org> Auto-Submit: Nate Chapin <japhet@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/master@{#911388} -- wpt-commits: 7eb7372a613fb3a4a7d4160d8292ac2b95b29864 wpt-pr: 29935
704306ece00c873fc35a24aa7cc6a7dc0826ec3c: Bug 1725431 [wpt PR 30009] - Test that dynamically adding display: none; to ::backdrop removes it, a=testonly
Tim Nguyen <ntim@apple.com> - Fri, 13 Aug 2021 14:31:34 +0000 - rev 589273
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725431 [wpt PR 30009] - Test that dynamically adding display: none; to ::backdrop removes it, a=testonly Automatic update from web-platform-tests Test that dynamically adding display: none; to ::backdrop removes it -- wpt-commits: fcc6453281a7583763ba7a2f3f06ae23c32cc494 wpt-pr: 30009
9e234247ff51d8ba2a263392fb3a489f53b589a1: Bug 1725426 [wpt PR 30008] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 12 Aug 2021 17:35:07 +0000 - rev 589272
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725426 [wpt PR 30008] - Update wpt metadata, a=testonly wpt-pr: 30008 wpt-type: metadata
f575ab9c204390335497eae003a8f812b95f152b: Bug 1725426 [wpt PR 30008] - Update lifecycle to clean from popup.open, a=testonly
Mason Freed <masonf@chromium.org> - Fri, 13 Aug 2021 14:31:25 +0000 - rev 589271
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725426 [wpt PR 30008] - Update lifecycle to clean from popup.open, a=testonly Automatic update from web-platform-tests Update lifecycle to clean from popup.open There is a resize observer used by <popup> to detect when it has been resized, which is one of the "light-dismiss" conditions. Because resize observer always fires once on the first Paint, there was a case where the behavior from JS was confusing/ incorrect. Essentially, if you open the popup and then immediately (synchronously) change the size of the popup, it would not close. With this change, popup.open() forces a rendering lifecycle. This CL also splits out the resize tests for popup into a separate file, and removes the usage of setTimeout(), which was previously buttering over this bug. Thanks to wanming.lin@ for pointing this out in [1]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/3084482 Bug: 1197633 Change-Id: I733f1215799980d0ed922cf8d8d312cbdcc140b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3089750 Auto-Submit: Mason Freed <masonf@chromium.org> Commit-Queue: Ionel Popescu <iopopesc@microsoft.com> Reviewed-by: Ionel Popescu <iopopesc@microsoft.com> Cr-Commit-Position: refs/heads/master@{#911345} -- wpt-commits: 2cb04aa75b704fc49e5f97751e19d22286b629a0 wpt-pr: 30008
be37610a17dd6683ea47d403b9faf1471e356eac: Bug 1723339 [wpt PR 29860] - Fix: Test errors in workers don't have an associated stack trace, a=testonly
Andreu Botella <abb@randomunok.com> - Fri, 13 Aug 2021 14:31:19 +0000 - rev 589270
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1723339 [wpt PR 29860] - Fix: Test errors in workers don't have an associated stack trace, a=testonly Automatic update from web-platform-tests Fix: Test errors in workers don't have an associated stack trace This typo, introduced in #8748, had `undefined` being passed as the third argument to `Tests.prototype.set_status`, which made test errors in worker tests not have an associated stack trace. -- wpt-commits: 1d03eb33639c1cca2f69beac69cbae9f8db6dff8 wpt-pr: 29860
b7689ac02082100bbbdb791328725ab13c1fc7ee: Bug 1725342 [wpt PR 30007] - Revert "Test anonymous iframe in cross-origin-isolated context.", a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 13 Aug 2021 14:31:14 +0000 - rev 589269
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725342 [wpt PR 30007] - Revert "Test anonymous iframe in cross-origin-isolated context.", a=testonly Automatic update from web-platform-tests Revert "Test anonymous iframe in cross-origin-isolated context." This reverts commit 10df1f70fd4e263ac1d30b26685c84404756e13e. Reason for revert: Flaky; e.g. https://ci.chromium.org/ui/p/chromium/builders/ci/Mac10.15%20Tests%20(dbg)/2139/overview Original change's description: > Test anonymous iframe in cross-origin-isolated context. > > Instead of crashing, relax checks to allow anonymous iframe inside > cross-origin-isolated context. > > Add a WPT test asking interesting questions about when the > cross-origin-isolated capability is delegated toward the anonymous > iframe (=open question). > > In any case, the anonymous iframe must never be blocked, which this test > tests too. > > Bug: 1237018 > Change-Id: I973a98ccc58c7ee8399052a53ef2b2f3f5610f59 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3074564 > Commit-Queue: Camille Lamy <clamy@chromium.org> > Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> > Reviewed-by: Camille Lamy <clamy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#910303} Bug: 1237018 Change-Id: I6e2c12c5acc010db28bf0161877d7fa18b0255f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3086571 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Owners-Override: Morten Stenshorne <mstensho@chromium.org> Auto-Submit: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#911226} -- wpt-commits: 241c2cc9bc2e70fa39ccc691e050a4cfb4d01ece wpt-pr: 30007
2e90444857f23cd93eede53a387c99a40fa42099: Bug 1725292 [wpt PR 30003] - Set Accept request header for Subresource WebBundle requests, a=testonly
Kunihiko Sakamoto <ksakamoto@chromium.org> - Fri, 13 Aug 2021 14:31:07 +0000 - rev 589268
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725292 [wpt PR 30003] - Set Accept request header for Subresource WebBundle requests, a=testonly Automatic update from web-platform-tests Set Accept request header for Subresource WebBundle requests We are going to make some breaking changes to the WebBundle format. In preparation for that, this sets "Accept: application/webbundle;v=b1" header to requests for <link rel="webbundle"> to tell the server side which version of WebBundle the browser supports. Bug: 1238641 Change-Id: Ibf5b89fe17324fab5419ac3ae3e14c8095e4f878 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3088718 Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#911149} -- wpt-commits: 22058da525739d0b2b250231f4c7d7cc6d5da2ab wpt-pr: 30003
1fbbe058293d826ecc83b2de7465f5678ca05ec5: Bug 1725225 [wpt PR 29998] - Break floats inside self-collapsing blocks correctly., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 13 Aug 2021 14:31:02 +0000 - rev 589267
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725225 [wpt PR 29998] - Break floats inside self-collapsing blocks correctly., a=testonly Automatic update from web-platform-tests Break floats inside self-collapsing blocks correctly. Even if the BFC block-offset is unknown when finishing layout of a block (this can happen if the block is self-collapsing), we still need to FinalizeForFragmentation(), in order to detect any breaks inside child floats, so that the break gets propagated correctly. If the initial optimistic BFC block-offset guess was correct, we won't lay out again with a forced block-offset identical to the optimistic one. So this is our only chance. Just use the "expected" block-offset if there's no BFC block-offset set. Among the new tests, only float-in-self-collapsing-block-000.html were failing without this, but I also added another test to verify that we don't get stuck with an incorrect optimistic guess. Bug: 1238508 Change-Id: Id70a4fc9a897ade0801dc1993742d2ba14209ad5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3087457 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#910990} -- wpt-commits: 30332a8593b2d8819573b7291bf7211222b6c358 wpt-pr: 29998
8c90f6db1931df853fd40cba997fa1dd3e65a112: Bug 1725093 [wpt PR 29982] - [TablesNG] Fix rowspan cell height distribution over percentage rows, a=testonly
Aleks Totic <atotic@chromium.org> - Fri, 13 Aug 2021 14:30:56 +0000 - rev 589266
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725093 [wpt PR 29982] - [TablesNG] Fix rowspan cell height distribution over percentage rows, a=testonly Automatic update from web-platform-tests [TablesNG] Fix rowspan cell height distribution over percentage rows Bug: when rowspanned cell distributed its height over rows that were all percentage sized, no height would be distributed. The problem was that when percentage resolution block size is indefinite, percentage rows were not treated as percentage rows. They were also not treated as empty rows either. Solution: treat percentage rows as empty rows when percentage resolutions size is indefinite. Bug: 1237879 Change-Id: I775b5ee5a0bdd7b8ec90f23d49642a3ba90a468b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3088159 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#910971} -- wpt-commits: 69528a9cb7488f69aee19f2e2f5ce685c03c72f4 wpt-pr: 29982
a829bf6afcf216e2041ef39ea1b18da75c0f8f08: Bug 1725083 [wpt PR 29981] - Add a WPT for .class selector styling of XML elements, a=testonly
Mason Freed <masonf@chromium.org> - Fri, 13 Aug 2021 14:30:51 +0000 - rev 589265
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725083 [wpt PR 29981] - Add a WPT for .class selector styling of XML elements, a=testonly Automatic update from web-platform-tests Add a WPT for .class selector styling of XML elements The [1] CL had to get reverted, but the test from that CL still makes sense to land, so it's available to other browsers, plus ready for if/when someone tackles a fix again. [1] https://chromium-review.googlesource.com/c/chromium/src/+/3077706 Bug: 649444 Change-Id: I9f3648df09da12bb85c1d40ef8e9507dcce49ce5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3088056 Commit-Queue: Mason Freed <masonf@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Reviewed-by: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/master@{#910914} -- wpt-commits: 5998702977e2e7b478c55474781ccd55fd08f80b wpt-pr: 29981
6b4bb2f4b081d255b3b94f6ccead7e75a6cf99e6: Bug 1725150 [wpt PR 29989] - [webmessaging] Removing duplicate test, a=testonly
Gabriela Sampaio <gaby.sampaio@gmail.com> - Fri, 13 Aug 2021 14:30:41 +0000 - rev 589264
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725150 [wpt PR 29989] - [webmessaging] Removing duplicate test, a=testonly Automatic update from web-platform-tests [webmessaging] Removing duplicate test (#29989) This fixes #29546. This test is a duplicate of [with-options/one-arg](https://github.com/web-platform-tests/wpt/blob/master/webmessaging/with-options/one-arg.html). For this reason, it can be deleted from the repository. -- wpt-commits: 63cad6de6de0544139b839b43985b3dcb48e458f wpt-pr: 29989
ea29fcfa51389ef405ab440169b2be302d1936fd: Bug 1725176 [wpt PR 29991] - Implement StyleVariables::operator=, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Fri, 13 Aug 2021 14:30:36 +0000 - rev 589263
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725176 [wpt PR 29991] - Implement StyleVariables::operator=, a=testonly Automatic update from web-platform-tests Implement StyleVariables::operator= StyleInheritedVariables uses the assignment operator, but it's not implemented correctly. Fixed: 1238686 Change-Id: I2cc41d9ddf5b9959a21671f80702a76cec556ed8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3086699 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#910876} -- wpt-commits: c5776eadb17bbb7e9d970cd5d8bf6b799f983ba0 wpt-pr: 29991
6e2e6d13dedaaa97fb8b8dd7b8ea3ac1ee02af2d: Bug 1725002 [wpt PR 29972] - [LayoutNG] Break token for new column before spanner, a=testonly
Alison Maher <almaher@microsoft.com> - Fri, 13 Aug 2021 14:30:31 +0000 - rev 589262
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725002 [wpt PR 29972] - [LayoutNG] Break token for new column before spanner, a=testonly Automatic update from web-platform-tests [LayoutNG] Break token for new column before spanner In CL:3018723, logic was added to the column layout algorithm to lay out any OOF descendants when we find a spanner to ensure that any OOF descendants found before a spanner are actually laid out before the spanner. If a new column was created for an OOF before the spanner, we wouldn't end up creating a column break token for that new column if the OOF didn't break. This CL adds logic to NGSimplifiedOOFLayoutAlgorithm to make sure that a break token is created for the column in this case. Additionally, if any columns are added after the spanner, we would end up crashing because the new column created for the OOF was not taken into account when adding the subsequent column (i.e. the sequence number and consumed block size were incorrect, and the subsequent column was added to the flow thread at the wrong index). To fix this, update the next column break token in MulticolPartWalker to the break token of new column added for the OOF. In order for layout to continue correctly from this new break token, any child break tokens from the previous column needed to be copied over to the new column generated during OOF layout. Otherwise, those children would not resume layout after the spanner. In addition, if an existing column fragment was replaced via NGSimplifiedOOFLayoutAlgorithm, and it had a child that had broken due to a break before, we would miss adding that child break token via child_iterator_. To fix this, add any child break tokens from the old fragment that were the result of a break before prior to simplified layout completion. Bug: 1237247 Change-Id: I55c73fc36a604e858dde5859f65a1ca66023e54a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3082315 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#910828} -- wpt-commits: 1bce3fabaaf18dda576d83f64f3ef03bdd647e3b wpt-pr: 29972
2e3eec05dacd8249eab952a3b8ed1efdb1bf4c6c: Bug 1725096 [wpt PR 29983] - [GridNG] Fix auto-placement with items spanning multiple rows, a=testonly
Ethan Jimenez <ethavar@microsoft.com> - Fri, 13 Aug 2021 14:30:23 +0000 - rev 589261
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725096 [wpt PR 29983] - [GridNG] Fix auto-placement with items spanning multiple rows, a=testonly Automatic update from web-platform-tests [GridNG] Fix auto-placement with items spanning multiple rows Fixing a bug where grid items were incorrectly placed after an item spanning multiple rows; this happened because, when moving to the next major line, we didn't account for grid items that were placed and immediately removed from |items_overlapping_major_line_|. Bug: 1237036 Change-Id: I148be6871bc42b27164f2b40df743d766eaafa08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3077168 Commit-Queue: Ethan Jimenez <ethavar@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com> Cr-Commit-Position: refs/heads/master@{#910708} -- wpt-commits: 385d72a67b1e423d96b3f653811cf2875b216ed2 wpt-pr: 29983
b02d713afb03e6c172b26168f70baeef7e11fee4: Bug 1724974 [wpt PR 29971] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 11 Aug 2021 08:32:53 +0000 - rev 589260
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724974 [wpt PR 29971] - Update wpt metadata, a=testonly wpt-pr: 29971 wpt-type: metadata
daae6e02c92cdb8b88ab39dc646ea54af4b37245: Bug 1724974 [wpt PR 29971] - Fix crash when matching ':has' to uninserted elements, a=testonly
Byungwoo Lee <blee@igalia.com> - Fri, 13 Aug 2021 14:30:15 +0000 - rev 589259
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724974 [wpt PR 29971] - Fix crash when matching ':has' to uninserted elements, a=testonly Automatic update from web-platform-tests Fix crash when matching ':has' to uninserted elements Previous implementation didn't consider ':has' matching for elements without parent, which caused crashes. Fix those crashes by handling null parent cases, and added wpt tests. Bug: 1237789, 1237743 Change-Id: Ibed2665ab0e6ad26cc757ed0210eeabac3daab21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3086781 Commit-Queue: Byungwoo Lee <blee@igalia.com> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#910694} -- wpt-commits: f16be66f18e3072f02339e39b8fe77e7dfdcc2f8 wpt-pr: 29971
133844a051b5316788ced26b11e037e1dd3836ae: Bug 1724837 [wpt PR 29960] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 11 Aug 2021 00:05:55 +0000 - rev 589258
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724837 [wpt PR 29960] - Update wpt metadata, a=testonly wpt-pr: 29960 wpt-type: metadata
fb6bc417a77173fb2e3dfda3c3b0ab275f0e97f0: Bug 1724837 [wpt PR 29960] - [WebCodecs] Support SharedArrayBuffer everywhere., a=testonly
Dale Curtis <dalecurtis@chromium.org> - Fri, 13 Aug 2021 14:30:03 +0000 - rev 589257
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724837 [wpt PR 29960] - [WebCodecs] Support SharedArrayBuffer everywhere., a=testonly Automatic update from web-platform-tests [WebCodecs] Support SharedArrayBuffer everywhere. This adds a utility function and helper typedef, then updates all of the following to support [AllowShared]: * Encoded(Audio|Video)Chunk both construction and copyTo(). * AudioData both construction and copyTo(). * AudioDecoderConfig.description * VideoDecoderConfig.description Tests are added for all of this. Fixed: 1238091 Change-Id: I2a4f52e552816868f91f9c62733499076bd20a8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3083156 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Dan Sanders <sandersd@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#910542} -- wpt-commits: 9e043a72138c38fa87d9069aec82b0c5ab215e0b wpt-pr: 29960
f3f71d950b2bdff1954e2083d2b6944de941bc60: Bug 1725005 [wpt PR 29974] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Aug 2021 22:48:12 +0000 - rev 589256
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725005 [wpt PR 29974] - Update wpt metadata, a=testonly wpt-pr: 29974 wpt-type: metadata
252b414190ab85da28e0e5a06c64b73194a2a013: Bug 1725005 [wpt PR 29974] - App history: implement updateCurrent(), a=testonly
Domenic Denicola <domenic@chromium.org> - Fri, 13 Aug 2021 14:29:50 +0000 - rev 589255
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725005 [wpt PR 29974] - App history: implement updateCurrent(), a=testonly Automatic update from web-platform-tests App history: implement updateCurrent() Follows https://github.com/WICG/app-history/pull/146. Bug: 1183545 Change-Id: Iabf64f2363906a2c7f2ecbd4e7c4a0e48c0f1522 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3086123 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#910469} -- wpt-commits: e14d88e66c63b158aaca534f8b6b3edb53f2edcc wpt-pr: 29974
765b69dbb338b72367ba8798ea5ea6aca35b1783: Bug 1724761 [wpt PR 29947] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Aug 2021 22:26:42 +0000 - rev 589254
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724761 [wpt PR 29947] - Update wpt metadata, a=testonly wpt-pr: 29947 wpt-type: metadata
c26da8d63eabe33189ed5788d0a3db0320f8f2d5: Bug 1724761 [wpt PR 29947] - Highlight API: Invalidate Highlights before paint, a=testonly
Fernando Fiori <ffiori@microsoft.com> - Fri, 13 Aug 2021 14:29:36 +0000 - rev 589253
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724761 [wpt PR 29947] - Highlight API: Invalidate Highlights before paint, a=testonly Automatic update from web-platform-tests Highlight API: Invalidate Highlights before paint - Move ValidateHighlightMarkers() call in paint phase to before calling PaintTree(). By rebuilding HighlightMarkers in paint phase after PaintTree() there was invalidation that would be repainted in the next frame paint, which wasn't being triggered unless there was some external interaction or DOM manipulation. Change-Id: I042913b823141f2b4c15c0206f227a6b623a4d35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3082151 Commit-Queue: Fernando Fiori <ffiori@microsoft.com> Reviewed-by: Dan Clark <daniec@microsoft.com> Reviewed-by: Stefan Zager <szager@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Daniel Libby <dlibby@microsoft.com> Cr-Commit-Position: refs/heads/master@{#910456} -- wpt-commits: 0f94ca65282ba94a40f7d28f704a90aa5dce93e5 wpt-pr: 29947
949e0f5113f1e2b8069f873a8766618237c61788: Bug 1725018 [wpt PR 29977] - Revert "Make classlist update for XML namespace nodes", a=testonly
Mason Freed <masonf@chromium.org> - Fri, 13 Aug 2021 14:29:28 +0000 - rev 589252
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1725018 [wpt PR 29977] - Revert "Make classlist update for XML namespace nodes", a=testonly Automatic update from web-platform-tests Revert "Make classlist update for XML namespace nodes" This reverts commit 5e25e22bb1642b26bc87e097ca00f54dd6ed8b88. Reason for revert: Many perf regressions: https://bugs.chromium.org/p/chromium/issues/list?q=id%3A1238218%2C1238219%2C1238224%2C1238235%2C1238239%2C1238244%2C1238245%2C1238247%2C1238285&can=2 Original change's description: > Make classlist update for XML namespace nodes > > Prior to this CL, CSS selectors like `.classname` would not match > XML namespace elements that had a `class` attribute with a value > of `classname`. However, `*[class~="classname"]` would match those > elements, querySelectorAll() would also match, and (perhaps most > importantly), Gecko, Webkit, and the spec all indicated that these > elements should be matched: > > https://dom.spec.whatwg.org/#dom-element-classname > > This could cause a minor perf regression, since ElementRareData will > be attached in more cases (memory regression), and the early-outs > in UpdateClassList have been removed (speed regression). I am > hopeful that these should be minor for ordinary HTML usage, but > we'll see. > > Fixed: 649444 > Change-Id: Ic846722830d76df801d2a8e33c360bfa41822cf6 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3077706 > Commit-Queue: Mason Freed <masonf@chromium.org> > Auto-Submit: Mason Freed <masonf@chromium.org> > Reviewed-by: Rune Lillesveen <futhark@chromium.org> > Cr-Commit-Position: refs/heads/master@{#910038} Change-Id: Ie5cb1955adf7638d11d1a850d4a6201384141ea6 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3086222 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/master@{#910450} -- wpt-commits: 5b48151e2dbddd3ea14f146ca8b782e6f76a8a17 wpt-pr: 29977
acc2b1bc0665e1ec8c73f0b4a809332feb543de1: Bug 1724853 [wpt PR 29966] - Add duration to opus encoder output, a=testonly
Thomas Guilbert <tguilbert@chromium.org> - Fri, 13 Aug 2021 14:29:11 +0000 - rev 589251
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724853 [wpt PR 29966] - Add duration to opus encoder output, a=testonly Automatic update from web-platform-tests Add duration to opus encoder output This CL adds duration metadata to encoded chunks output by opus encoder. Bug: 1235153 Change-Id: I0c92fa809c9cf4dd1d609b0ac44dcfd7486a6fb2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3084018 Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Reviewed-by: Eugene Zemtsov <eugene@chromium.org> Cr-Commit-Position: refs/heads/master@{#910429} -- wpt-commits: 983507742b492dd23a8ce6788180ef1b674d16a9 wpt-pr: 29966
e8b9679bf605b40c391875432dfc319c5cf0fd8b: Bug 1724813 [wpt PR 29958] - MSE: Strengthen QuotaExceededError validation for fixing spec #288, a=testonly
Matt Wolenetz <wolenetz@chromium.org> - Fri, 13 Aug 2021 14:29:06 +0000 - rev 589250
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724813 [wpt PR 29958] - MSE: Strengthen QuotaExceededError validation for fixing spec #288, a=testonly Automatic update from web-platform-tests MSE: Strengthen QuotaExceededError validation for fixing spec #288 This change strengthens the checks that when an appendBuffer()'s internal steps are aborted due to QuotaExceededError exception within the "prepare append algorithm", the rest of the appendBuffer()'s steps are also aborted. Note that verifying the state of the implementations internal "input buffer" is not included in this change due to complexity of that verification. See https://github.com/w3c/media-source/issues/288. This change will help inform whether that issues' fix would be a breaking change for implementations that report results on https://wpt.fyi Change-Id: Iaba91eb739ca40d4633b15326871bd3635e16fbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3083226 Auto-Submit: Matthew Wolenetz <wolenetz@chromium.org> Commit-Queue: Will Cassella <cassew@google.com> Reviewed-by: Will Cassella <cassew@google.com> Cr-Commit-Position: refs/heads/master@{#910333} -- wpt-commits: 60bc5896a5ce5586303378fe7f92ff8c756970a2 wpt-pr: 29958
35298e31000218485a92c707a71902aa09a44d80: Bug 1722115 [wpt PR 29774] - Converted many scroll animation tests to not use timeRange, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Fri, 13 Aug 2021 14:28:54 +0000 - rev 589249
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1722115 [wpt PR 29774] - Converted many scroll animation tests to not use timeRange, a=testonly Automatic update from web-platform-tests Converted many scroll animation tests to not use timeRange (#29774) The tests converted in this CL were the one that were fairly straight forward to remove timeRange. Another follow up CL will contain the slightly more involved conversions. I also cleaned up the formatting for many of the tests so that they are a bit more consistent. Bug: 1216655 Change-Id: Ia62b32dede03eea9ed0040a684fdfb6e07a0baf1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3050732 Commit-Queue: Jordan Taylor <jortaylo@microsoft.com> Reviewed-by: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#909537} Co-authored-by: Jordan Taylor <jortaylo@microsoft.com> -- wpt-commits: bac5e0617f1abede4a433716eb5dcb432ba29607 wpt-pr: 29774
cf34fe1e93e7e847a9241913650df4cf48975165: Bug 1724844 [wpt PR 29961] - Fuzzy match for css/css-position/position-absolute-iframe-print-00*.sub.html, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Fri, 13 Aug 2021 14:28:40 +0000 - rev 589248
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724844 [wpt PR 29961] - Fuzzy match for css/css-position/position-absolute-iframe-print-00*.sub.html, a=testonly Automatic update from web-platform-tests Fuzzy match for css/css-position/position-absolute-iframe-print-00*.sub.html The test failed because of difference of some text antialias pixels due to compositing differences. Bug: 626703 Change-Id: I8871094306c6739d426afa2a2389862d0e07c52a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3083174 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#910330} -- wpt-commits: 3b89d6bfb4e225051123679087467527e5261bf4 wpt-pr: 29961
2f17f28e900c20874ef0ab1ed37feea74da433c5: Bug 1724415 [wpt PR 29927] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Aug 2021 16:30:07 +0000 - rev 589247
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724415 [wpt PR 29927] - Update wpt metadata, a=testonly wpt-pr: 29927 wpt-type: metadata
cdd867c375a8a161b453acc336d38659680cc330: Bug 1724415 [wpt PR 29927] - Test anonymous iframe in cross-origin-isolated context., a=testonly
Arthur Sonzogni <arthursonzogni@chromium.org> - Fri, 13 Aug 2021 14:28:30 +0000 - rev 589246
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724415 [wpt PR 29927] - Test anonymous iframe in cross-origin-isolated context., a=testonly Automatic update from web-platform-tests Test anonymous iframe in cross-origin-isolated context. Instead of crashing, relax checks to allow anonymous iframe inside cross-origin-isolated context. Add a WPT test asking interesting questions about when the cross-origin-isolated capability is delegated toward the anonymous iframe (=open question). In any case, the anonymous iframe must never be blocked, which this test tests too. Bug: 1237018 Change-Id: I973a98ccc58c7ee8399052a53ef2b2f3f5610f59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3074564 Commit-Queue: Camille Lamy <clamy@chromium.org> Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Camille Lamy <clamy@chromium.org> Cr-Commit-Position: refs/heads/master@{#910303} -- wpt-commits: da3d99ed3339fb658276ae0cc81a02d818892b39 wpt-pr: 29927
053ba40d48d96c8558acda44809b4f94d617d34d: Bug 1724541 [wpt PR 29937] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 10 Aug 2021 15:57:32 +0000 - rev 589245
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724541 [wpt PR 29937] - Update wpt metadata, a=testonly wpt-pr: 29937 wpt-type: metadata
2bb33fb739ab4d31bf0ede022433315aa99869d5: Bug 1724541 [wpt PR 29937] - App history: implement reload() instead of no-arg navigate(), a=testonly
Domenic Denicola <domenic@chromium.org> - Fri, 13 Aug 2021 14:28:21 +0000 - rev 589244
Push 35618 by ksteuber@mozilla.com at Mon, 23 Aug 2021 23:38:14 +0000
Bug 1724541 [wpt PR 29937] - App history: implement reload() instead of no-arg navigate(), a=testonly Automatic update from web-platform-tests App history: implement reload() instead of no-arg navigate() This also fixes the exception order in navigate(). Fixed: 1211490 Fixed: 1220156 Change-Id: Ibe8b1296991b0dc621ca5f50a6fa4fc9041384a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3076387 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#910301} -- wpt-commits: a8f15155f3a2465abeb40c7b3c92018aeab2c8b1 wpt-pr: 29937