searching for reviewer(testonly)
b1bcf434531124f17595ca45e15808b0df21a147: Bug 1743230 - [wpt-sync] Update web-platform-tests to 43fb287da71d4c37d7604c410f9c49c33df41fc5, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 29 Nov 2021 09:45:08 +0000 - rev 600540
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743230 - [wpt-sync] Update web-platform-tests to 43fb287da71d4c37d7604c410f9c49c33df41fc5, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 43fb287da71d4c37d7604c410f9c49c33df41fc5 wpt-type: landing
ec2128480e3055fd35f7c61cd7d2def2a29ea78e: Bug 1743209 [wpt PR 31763] - Use proper cleanup in dialog-focusing-steps-disconnected.html, a=testonly
Oriol Brufau <obrufau@igalia.com> - Mon, 29 Nov 2021 09:42:51 +0000 - rev 600539
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743209 [wpt PR 31763] - Use proper cleanup in dialog-focusing-steps-disconnected.html, a=testonly Automatic update from web-platform-tests Use proper cleanup in dialog-focusing-steps-disconnected.html See #31761 -- wpt-commits: 43fb287da71d4c37d7604c410f9c49c33df41fc5 wpt-pr: 31763
fbfa84e24b69c19dd19e02bfbc093f290efd1b3b: Bug 1743200 [wpt PR 31761] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 27 Nov 2021 00:27:11 +0000 - rev 600538
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743200 [wpt PR 31761] - Update wpt metadata, a=testonly wpt-pr: 31761 wpt-type: metadata
2f25181ea69e2bc5644a716549e11e05aee567b4: Bug 1743200 [wpt PR 31761] - Use proper cleanup in dialog-focusing-steps-inert.html, a=testonly
Oriol Brufau <obrufau@igalia.com> - Mon, 29 Nov 2021 09:42:36 +0000 - rev 600537
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743200 [wpt PR 31761] - Use proper cleanup in dialog-focusing-steps-inert.html, a=testonly Automatic update from web-platform-tests Use proper cleanup in dialog-focusing-steps-inert.html The test was just cleaning up at the end of the test(), but the code was not reached if some assert failed, making the following test() fail too. The proper way to clean up is with add_cleanup(). This change makes the 2nd test pass in Firefox and Chromium. -- wpt-commits: 85b644d6794ed490de95693d23411342afe592da wpt-pr: 31761
33106bf7544d7e24aa260c99b633f398e1a99e24: Bug 1743034 [wpt PR 31749] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 27 Nov 2021 00:21:31 +0000 - rev 600536
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743034 [wpt PR 31749] - Update wpt metadata, a=testonly wpt-pr: 31749 wpt-type: metadata
9977644b1d5b2dfed9a00cc1b3bb956ed2a28285: Bug 1743034 [wpt PR 31749] - Add scroll smoothness check to scroll-snap test with keyboard input, a=testonly
Kevin Ellis <kevers@chromium.org> - Mon, 29 Nov 2021 09:42:28 +0000 - rev 600535
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743034 [wpt PR 31749] - Add scroll smoothness check to scroll-snap test with keyboard input, a=testonly Automatic update from web-platform-tests Add scroll smoothness check to scroll-snap test with keyboard input Previous the test only ensure that we reached the expected endpoint, but the transition could be smooth or a sudden jump. With the patch, we count the number of steps before reaching the endpoint. During experimental testing, hundreds of scroll events were received during the course of a smooth scroll. The required target was set to 2, to catch an immediate jump and to non-flake when a testing machine is bogged down. Bug: 1273921 Change-Id: Ie24a5fa2795af3860fe38bdd93522dde2f39365b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3302851 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/main@{#945701} -- wpt-commits: 2b51200c5cd24e97f6cef54dabe9791cac64e116 wpt-pr: 31749
c1df16cbdc465f09d6447b6e9ee52bd2ebfceb53: Bug 1743161 [wpt PR 31758] - Test that ::backdrop receives events for the associated element, a=testonly
Tim Nguyen <nt1m@users.noreply.github.com> - Mon, 29 Nov 2021 09:42:24 +0000 - rev 600534
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743161 [wpt PR 31758] - Test that ::backdrop receives events for the associated element, a=testonly Automatic update from web-platform-tests Test that ::backdrop receives events for the associated element (#31758) -- wpt-commits: 2c4d3746975998c5e0fd3ca8fd33f7dc23cb4bd2 wpt-pr: 31758
092883f226a73e30cc20b852032320b5a474722a: Bug 1742978 [wpt PR 31745] - [Canvas] Adding more layer reference tests to WPT, a=testonly
Juanmi Huertas <juanmihd@google.com> - Mon, 29 Nov 2021 09:42:17 +0000 - rev 600533
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742978 [wpt PR 31745] - [Canvas] Adding more layer reference tests to WPT, a=testonly Automatic update from web-platform-tests [Canvas] Adding more layer reference tests to WPT This CL adds a couple of more tests to the WPT suite, one for global composite operation and the other one verifying that endLayer will restore the style of the layer. Bug: 1231615 Change-Id: Ideadb4bcb74f1a82a5b6451a088bf2f36d364232 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3301067 Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Juanmi Huertas <juanmihd@chromium.org> Cr-Commit-Position: refs/heads/main@{#945661} -- wpt-commits: 9948799493758cda980ec903cb8cbb8d1ba97330 wpt-pr: 31745
374430bb8057504066d3d03804c945e40ff3df4c: Bug 1742895 [wpt PR 31741] - [Canvas] Adding fuzziness to Layers nested tests, a=testonly
Juanmi Huertas <juanmihd@google.com> - Mon, 29 Nov 2021 09:42:12 +0000 - rev 600532
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742895 [wpt PR 31741] - [Canvas] Adding fuzziness to Layers nested tests, a=testonly Automatic update from web-platform-tests [Canvas] Adding fuzziness to Layers nested tests The layer nested test was failing due to unnoticeable differences in the RGB values of the content. The images are visually identical, so the test is correct. Bug: 1231615 Change-Id: I7f73b9ecf16256690d66f9f4931704029461d756 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3301060 Commit-Queue: Juanmi Huertas <juanmihd@chromium.org> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/main@{#945653} -- wpt-commits: c1a07be656a2e9bd56c9b5ea4a14e1fc612a0014 wpt-pr: 31741
03dbca4861837738416031620e8ba8814b6a5fd1: Bug 1743037 [wpt PR 31750] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 18:43:49 +0000 - rev 600531
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743037 [wpt PR 31750] - Update wpt metadata, a=testonly wpt-pr: 31750 wpt-type: metadata
a725815930cf40b5afae9475cd3a2ec88fe01166: Bug 1743037 [wpt PR 31750] - Fix text painting for ::target-text & ::highlight, a=testonly
Manuel Rego Casasnovas <rego@igalia.com> - Mon, 29 Nov 2021 09:42:04 +0000 - rev 600530
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743037 [wpt PR 31750] - Fix text painting for ::target-text & ::highlight, a=testonly Automatic update from web-platform-tests Fix text painting for ::target-text & ::highlight ::target-text & ::highlight pseudo-elements were not painting the text if the originating element color was transparent. This patch fixes this removing two checks in NGHighlightPainter::Paint(). BUG=1273943 TEST=web_tests/external/wpt/css/css-highlight-api/painting/custom-highlight-painting-017.html TEST=web_tests/external/wpt/css/css-pseudo/target-text-007.html Change-Id: Ie8198e8cf37d6ef89cdee341e84b6bc36ad6ec84 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3302311 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/main@{#945638} -- wpt-commits: 9263c77a44949129fde66630de5dc286083f20ee wpt-pr: 31750
a297a573bf04cfa1fa40416ebd00605a55fc4795: Bug 1743080 [wpt PR 31755] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 12:11:45 +0000 - rev 600529
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743080 [wpt PR 31755] - Update wpt metadata, a=testonly wpt-pr: 31755 wpt-type: metadata
ea7b7d0ac8ab549afd8c083c3fedbd3f5d895ca2: Bug 1743080 [wpt PR 31755] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233514, a=testonly
Tim Nguyen <nt1m@users.noreply.github.com> - Mon, 29 Nov 2021 09:41:45 +0000 - rev 600528
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743080 [wpt PR 31755] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233514, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233514 (#31755) -- wpt-commits: 5a6f1ee2c25aa1f01ca09d853a2e5cb3b3a43ad6 wpt-pr: 31755
dba8f25c8faca8f6cb648f478d2926f800e12a35: Bug 1742997 [wpt PR 31746] - Ignore items generated for line breaks at the beggining of the text, a=testonly
Javier Fernández García-Boente <jfernandez@igalia.com> - Mon, 29 Nov 2021 09:41:41 +0000 - rev 600527
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742997 [wpt PR 31746] - Ignore items generated for line breaks at the beggining of the text, a=testonly Automatic update from web-platform-tests Ignore items generated for line breaks at the beggining of the text In r944940 we've added some new logic to the AppendTextReusing function in the NGInlineItemsBuilder class to dected some inconsitencies in the items list related to control items added to force line breaks. The bugs 1273593 and 1273688 decribe some invalid access to the text array, since the text's legnth was 0 and we were initializing the index at length - 1; being this index of type wtf_size_t, this code lead to an arithmetic overflow, hence an index out of the text array range. We could have fixed this specific issue by using an integer type and changing the loop clauses to ensure the index is always positive. But doing so we are hit by a different DCHECK violation, caused by a difference in the length of the NGOffsetMapping current and new text, performed as part of some integrity checks being done in the NGInlineNode::PrepareLayout function. The root cause of the integrity checks failure is that we are restoring control items at the position 0 of the text, which indicates an invalid state of the item list being processed. This is a similar issue than the one described in 1263567, already fixed in the mentioned r944940 revision. The solution to both problems would be to ignore control items generated to force line breaks when the text_ length is 0. Bug: 1263567, 1273593, 1273688 Change-Id: Ib743a94e91d331d7344b817194994bc6630ff2c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3302669 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/main@{#945572} -- wpt-commits: 3c77bf496e9c506b6ce32cf5866fa3a97f95f881 wpt-pr: 31746
d8bef1eec47ec7b41f9fd025ee3248a989dadff6: Bug 1743056 [wpt PR 31030] - [WebID] Support navigator.credentials.get for WebID, a=testonly
Yi Gu <yigu@chromium.org> - Mon, 29 Nov 2021 09:41:34 +0000 - rev 600526
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1743056 [wpt PR 31030] - [WebID] Support navigator.credentials.get for WebID, a=testonly Automatic update from web-platform-tests [WebID] Support navigator.credentials.get for WebID This patch migrates `get` from `navigator.id` to `navigator.credentials` and adds/updates tests to reflect the change. Bug: 1252968 Change-Id: I4fdfa230bfbe62f68d1d32510fb63b77c20525c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3192716 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by: dsinclair <dsinclair@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/main@{#945514} -- wpt-commits: ee91ed5f32a2c5b9bd67b1621b68db846c7f6531 wpt-pr: 31030
55f02638b8dde51e44494eccfdd721eee3e88e71: Bug 1737880 [wpt PR 31387] - Update letterSpacing and wordSpacing to accept Strings, a=testonly
Yi Xu <yiyix@chromium.org> - Mon, 29 Nov 2021 09:41:28 +0000 - rev 600525
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1737880 [wpt PR 31387] - Update letterSpacing and wordSpacing to accept Strings, a=testonly Automatic update from web-platform-tests Update letterSpacing and wordSpacing to accept Strings letterSpacing and wordSpacing used to take doubles that represent spacing in pixels, which limited users from specify spacing relative to font size, ex: ems. This patch now make letterSpacing and wordSpacing to take Strings, so users has the flexibility to use different units as em, px, cm, mm, etc. WPT test will be added in the next cl. example of usage: ctx.letterSpacing = 0.3em; ctx.wordSpacing = 1inch; explainer: https://github.com/fserb/canvas2D/blob/master/spec/text-modifiers.md Bug: 1263632 Change-Id: I40a219a57462ce749b44de6e7c3b5c885753c95e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3244342 Commit-Queue: Yi Xu <yiyix@chromium.org> Reviewed-by: Fernando Serboncini <fserb@chromium.org> Reviewed-by: Justin Novosad <junov@chromium.org> Cr-Commit-Position: refs/heads/main@{#945498} -- wpt-commits: 99b36b6cc3df862d726045e36a80ef27959b345d wpt-pr: 31387
6a2a665a298d930e25f001f1755e9139718238b1: Bug 1742942 [wpt PR 31743] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 00:22:55 +0000 - rev 600524
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742942 [wpt PR 31743] - Update wpt metadata, a=testonly wpt-pr: 31743 wpt-type: metadata
e05a436f18e3943c350beddf487bcf00290d2195: Bug 1742942 [wpt PR 31743] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233489, a=testonly
Antti Koivisto <antti@apple.com> - Mon, 29 Nov 2021 09:41:18 +0000 - rev 600523
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742942 [wpt PR 31743] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233489, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233489 (#31743) -- wpt-commits: 248bbac0c35ed8deb369112d859ed9c93fd8afe2 wpt-pr: 31743
a801937914c2696c31b934cd5a1620b9b1d12f80: Bug 1742186 [wpt PR 31692] - [FedCM] Implement the DOM part of revoke(), a=testonly
Christian Biesinger <cbiesinger@chromium.org> - Mon, 29 Nov 2021 09:41:09 +0000 - rev 600522
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742186 [wpt PR 31692] - [FedCM] Implement the DOM part of revoke(), a=testonly Automatic update from web-platform-tests [FedCM] Implement the DOM part of revoke() As specified in https://wicg.github.io/FedCM/#browser-api-revocation This finishes the revocation API implementation. Bug: 1263140 Change-Id: I390e16fc5e2a9290c2888021151be983fe043a03 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3293941 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Yi Gu <yigu@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/main@{#945475} -- wpt-commits: 643a490eacdcf633e51c16c574b8dfb89a8b3b0f wpt-pr: 31692
811d8a224682718fd460134b3ba1d1aeacc9ac7b: Bug 1693839 [wpt PR 31695] - [Gecko Bug 1693839] [webdriver-client] Move module classes for WebDriver BiDi to their own directory., a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 29 Nov 2021 09:40:29 +0000 - rev 600521
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1693839 [wpt PR 31695] - [Gecko Bug 1693839] [webdriver-client] Move module classes for WebDriver BiDi to their own directory., a=testonly Automatic update from web-platform-tests [webdriver-client] Move module classes for WebDriver BiDi to their own directory. Differential Revision: https://phabricator.services.mozilla.com/D131604 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1693839 gecko-commit: 0dce12e803e358de869fb2c9eb068ee34af256fd gecko-reviewers: webdriver-reviewers, jgraham, jdescottes -- [webdriver-client] Move transport class for WebDriver BiDi into its own module. Differential Revision: https://phabricator.services.mozilla.com/D131605 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1693839 gecko-commit: 95d37ec74f93824d4990555c83055bc175ebd80f gecko-reviewers: webdriver-reviewers, jdescottes -- [wdspec] Added test to check args of log.entryAdded event. Differential Revision: https://phabricator.services.mozilla.com/D131606 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1693839 gecko-commit: 780ea53e87faa541b9200ce62e28e5e49ff4771a gecko-reviewers: webdriver-reviewers, jgraham, jdescottes -- Flake8 fixes -- wpt-commits: 5f9a585886640e656f8c73d34156b94c31d71a5b, b7e9c2bfb67fafdfbf38444e7e6b835b583c9905, 4901df8709faf3a0629f0b4363b4bbd05c22b029, 28ffee05ff66bea30350d75cb22e1267c7c3135f wpt-pr: 31695
f3a84709862ac4f623d77a9f02e3d346aa73cf13: Bug 1741766 [wpt PR 31668] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 12:02:31 +0000 - rev 600520
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1741766 [wpt PR 31668] - Update wpt metadata, a=testonly wpt-pr: 31668 wpt-type: metadata
a5182b97892b23553af2d1a6e5d88227f2577f67: Bug 1741766 [wpt PR 31668] - [inert] Add WPTs for interaction of inert attribute with modal dialog, a=testonly
Oriol Brufau <obrufau@igalia.com> - Sat, 27 Nov 2021 09:48:14 +0000 - rev 600519
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1741766 [wpt PR 31668] - [inert] Add WPTs for interaction of inert attribute with modal dialog, a=testonly Automatic update from web-platform-tests [inert] Add WPTs for interaction of inert attribute with modal dialog https://html.spec.whatwg.org/multipage/interaction.html#inert is clear: > While document is so blocked [by a modal dialog], every node that is > connected to document, with the exception of the subject element and > its shadow-including descendants, must be marked inert. (The elements > excepted by this paragraph can additionally be marked inert through > other means; being part of a modal dialog does not "protect" a node > from being marked inert.) However, both Firefox and WebKit ignore this, and let modal dialogs escape the inertness set by an ancestor with the 'inert' attribute. There is also an interesting case: when the modal dialog is the root element. Firefox handles this fine, but Chromium used to fail the test, and WebKit directly crashes. Bug: 692360 Change-Id: Ie52201a1f31790392180c96a9e08be1b5eee86d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3290703 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#945411} -- wpt-commits: 06916c31d3c09191e3865bab05adfff2e6362662 wpt-pr: 31668
3ce824b75205b3b3f5fae387af1708c04d27ff6e: Bug 1742084 [wpt PR 31681] - Automatically detect Chrome browser binary if it exists, a=testonly
Daniel Smith <56164590+DanielRyanSmith@users.noreply.github.com> - Sat, 27 Nov 2021 09:48:09 +0000 - rev 600518
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742084 [wpt PR 31681] - Automatically detect Chrome browser binary if it exists, a=testonly Automatic update from web-platform-tests Fix bug locating the Chrome binary (#31681) -- wpt-commits: 52dca517e77f6adb74cbddffa845a0bdf6acfb9c wpt-pr: 31681
b09ba3a52dd160f6fbf4591cba62175a8f4f7693: Bug 1733562 [wpt PR 31040] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 12:01:19 +0000 - rev 600517
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1733562 [wpt PR 31040] - Update wpt metadata, a=testonly wpt-pr: 31040 wpt-type: metadata
bab641f2a55059e9a4106134f23e1e867ed3dbab: Bug 1733562 [wpt PR 31040] - [Clipboard API] Add support for Promise to Blobs in clipboard item., a=testonly
Anupam Snigdha <snianu@microsoft.com> - Sat, 27 Nov 2021 09:47:59 +0000 - rev 600516
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1733562 [wpt PR 31040] - [Clipboard API] Add support for Promise to Blobs in clipboard item., a=testonly Automatic update from web-platform-tests [Clipboard API] Add support for Promise to Blobs in clipboard item. This patch adds promise support to `ClipboardItem` object. This helps the web author to call async write method without having to provide the Blob data synchronously. Authors can choose to resolve the promise later when the Blob data is available. This change does not break any existing code that only takes a Blob parameter while constructing `ClipboardItem` object, so this should not be considered as a breaking change. I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/8z0qWJ5Fztc/m/qJwfgMTxAAAJ?utm_medium=email&utm_source=footer Bug: 1014310 Change-Id: I5104c70e6f3e28591801f72165d7b9ec381bd04f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3169593 Commit-Queue: Anupam Snigdha <snianu@microsoft.com> Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/main@{#945323} -- wpt-commits: 2865f7276a9140a0f19f6ef5b9f5b3675a135bf0 wpt-pr: 31040
f33a851e0a6e1ef9323fea1a17ac79f397ec12d6: Bug 1742846 [wpt PR 31734] - Invalidate paint when CompositingContainer changes, a=testonly
Philip Rogers <pdr@chromium.org> - Sat, 27 Nov 2021 09:47:54 +0000 - rev 600515
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742846 [wpt PR 31734] - Invalidate paint when CompositingContainer changes, a=testonly Automatic update from web-platform-tests Invalidate paint when CompositingContainer changes PaintLayer::CompositingContainer may change when stacking changes. We mark the previous compositing container for repaint in |LayoutBoxModelObject::StyleWillChange| but also need to mark the new compositing container chain for repaint. Bug: 1271871 Change-Id: Ief05ea5c26ae27ebe2918db293ad8e17a5851a9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3300510 Auto-Submit: Philip Rogers <pdr@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/main@{#945205} -- wpt-commits: b6e9ffd765b9e0b4840b45a46f9ddbcf1aecf7fe wpt-pr: 31734
4b3603e563c395d378d6195f29a7f17744ef4daa: Bug 1742882 [wpt PR 31738] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 25 Nov 2021 00:28:42 +0000 - rev 600514
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742882 [wpt PR 31738] - Update wpt metadata, a=testonly wpt-pr: 31738 wpt-type: metadata
f1e6cacaef0f83fe497d3dfde9879f59cd850f6c: Bug 1742882 [wpt PR 31738] - Streams: fix tests for abort reason, a=testonly
Mattias Buelens <mattias@buelens.com> - Sat, 27 Nov 2021 09:47:44 +0000 - rev 600513
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742882 [wpt PR 31738] - Streams: fix tests for abort reason, a=testonly Automatic update from web-platform-tests Streams: fix tests for abort reason -- Test AbortController.abort(null) -- wpt-commits: cd0a25090b74df32b61be6ce91e3d43ecb65d8fb, 71c864f8bd7f855f12c81bfc7a1fc3ebf18657f3 wpt-pr: 31738
965fda79551f9121beb4eea1ec9893da2b1af703: Bug 1739747 [wpt PR 31535] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 12:00:08 +0000 - rev 600512
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1739747 [wpt PR 31535] - Update wpt metadata, a=testonly wpt-pr: 31535 wpt-type: metadata
2d48a7c4fc8e14f70a7647dc3802a9c1c7f55d3e: Bug 1739747 [wpt PR 31535] - Update PARAKEET API definitions and params for Ad Auction Service, a=testonly
Brandon Maslen <brandm@microsoft.com> - Sat, 27 Nov 2021 09:47:35 +0000 - rev 600511
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1739747 [wpt PR 31535] - Update PARAKEET API definitions and params for Ad Auction Service, a=testonly Automatic update from web-platform-tests Update PARAKEET API definitions and params for Ad Auction Service Updates idl definitions for PARAKEET API and related types. As part of this adds the mojom types/traits and associated ad auction service methods to accommodate the create/finalize ad calls. Initially the added methods do basic validation and call the associated service. The service will not currently make any calls to the PARAKEET service for valid calls; a future change will add this ability. Tests have been added to validate the associated mojo traits, service and DOM API parameters/valid and invalid conditions. Bug: 1249186 Change-Id: If280b19bc809abe25017fec6a5a594b724e8c0d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3265725 Commit-Queue: Brandon Maslen <brandm@microsoft.com> Reviewed-by: Russ Hamilton <behamilton@google.com> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/main@{#945133} -- wpt-commits: ab77b4b739b0fdcff41e34654142383cf4275100 wpt-pr: 31535
38a2d18f54f08e316966d1f8982df629aa6e04d1: Bug 1740441 [wpt PR 31578] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 26 Nov 2021 12:13:09 +0000 - rev 600510
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1740441 [wpt PR 31578] - Update wpt metadata, a=testonly wpt-pr: 31578 wpt-type: metadata
8ed8ed8df30e803c068c37f4a8c376d64b8d3fc4: Bug 1740441 [wpt PR 31578] - CSP: Do not strip non webby URL in reports., a=testonly
Arthur Sonzogni <arthursonzogni@chromium.org> - Sat, 27 Nov 2021 09:47:16 +0000 - rev 600509
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1740441 [wpt PR 31578] - CSP: Do not strip non webby URL in reports., a=testonly Automatic update from web-platform-tests CSP: Do not strip non webby URL in reports. In https://crbug.com/1264789, developers complained non HTTP/HTTPS URLs are not included in reports. The restriction was mostly introduced by: https://codereview.chromium.org/2002943002 for convenience, in order to reuse KURL::StrippedForUseAsReferrer. The drawback is that "webpack://node_modules/sample/script4.js" is transformed into "webpack", since its protocol is not http/https. This patch initially wanted to remove this restrictions by rewriting our own version of StrippedForUseAsReferrer, without the inconvenience, and most importantly, add 14 WPT test cases. Last minute, I wrote a specification: https://github.com/w3c/webappsec-csp/pull/527 and decided to prefer using an allow-list containing ['http', 'https'] instead of a block-list. As a result, 'webpack:' URLs continue to be stripped down to their scheme. Sorry... Note: There are some scheme we don't want to expose, like ['chrome-extension', 'moz-extension']. Bug: 1264789 Change-Id: Ia967c3122915a37b119321bb327e6c969d649020 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3263879 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/main@{#944975} -- wpt-commits: a4ee3de9da209b65ab902d63546bf2a96d454ba2 wpt-pr: 31578
9649b70b47eccb7419f2ac32e8b4f27ae225095a: Bug 1742419 [wpt PR 31701] - Don't reuse generated breaks when space sequences become non-leading, a=testonly
Javier Fernández García-Boente <jfernandez@igalia.com> - Sat, 27 Nov 2021 09:47:11 +0000 - rev 600508
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742419 [wpt PR 31701] - Don't reuse generated breaks when space sequences become non-leading, a=testonly Automatic update from web-platform-tests Don't reuse generated breaks when space sequences become non-leading The NNInlineItemsBuilder class is the responsible of creating the NGInlineItems list form the text nodes in the DOM tree. A special part of this logic is the one that inserts control items after a leading space sequence, in order to introduce forced-breaks in that position. When these leading space sequences are not in the paragraph's first line it means that they are preceded by a line-break element. Removing such break element triggers a new layout, since the DOM tree has changed. The NGInlineItemsBuilder logic tries to reuse the existing items when processing a new text layout. However, if a line-break element is removed, we should also remove any control item previously added to introduce forced-breaks, as commented before. The current code doesn't do that, leading to the buggy behavior described on the bug. This CL introduces an additional step in the AppendTextReusing function to detect these kind of "orphan" control items and ignore them when building the new items list. Bug: 1263567 Change-Id: Ie9ebadd4952efb491b983fba1cd2c6a7d7d1bf0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3290413 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/main@{#944940} -- wpt-commits: 893d36cb97c60085c4d5acb5a9d357efbcde7ad6 wpt-pr: 31701
1136f2c721df4f6a8b2a9f436a6f183e84b00e45: Bug 1742772 [wpt PR 31728] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233446, a=testonly
Manuel Rego Casasnovas <rego@igalia.com> - Sat, 27 Nov 2021 09:46:59 +0000 - rev 600507
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742772 [wpt PR 31728] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233446, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=233446 -- wpt-commits: 177488f9b76c83b4831b6ecd95c3b471d6b29ccc wpt-pr: 31728
fa713b8c12582e501855d3c3eda40d4f0615853c: Bug 1742423 [wpt PR 31702] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 24 Nov 2021 10:31:35 +0000 - rev 600506
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742423 [wpt PR 31702] - Update wpt metadata, a=testonly wpt-pr: 31702 wpt-type: metadata
7253b4a608abbb5a9acc86fa74afeae35c78504a: Bug 1742423 [wpt PR 31702] - CSP: WPT blockedURI about ws,wss schemes, a=testonly
Arthur Sonzogni <arthursonzogni@chromium.org> - Sat, 27 Nov 2021 09:46:46 +0000 - rev 600505
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742423 [wpt PR 31702] - CSP: WPT blockedURI about ws,wss schemes, a=testonly Automatic update from web-platform-tests CSP: WPT blockedURI about ws,wss schemes Check if the blockedURI in CSP violation reports allow ws/wss scheme and whether they are reported as-is or converted to http/https. See the following discussion: https://github.com/w3c/webappsec-csp/issues/532 Bug: None Change-Id: I7024544aefab002cecf71b7ebfb90e8c75d5889b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3295459 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/main@{#944889} -- wpt-commits: 10674aea9e50cc0057270d6c64b2452dd5f12fe4 wpt-pr: 31702
1615b5a17c8a612a0d772daa1ab614cc2a66ea4b: Bug 1742212 [wpt PR 31694] - Validate viewBox when its value is changed in JavaScript, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Sat, 27 Nov 2021 09:46:40 +0000 - rev 600504
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742212 [wpt PR 31694] - Validate viewBox when its value is changed in JavaScript, a=testonly Automatic update from web-platform-tests Validate viewBox when its value is changed in JavaScript - Add SVGFitToViewBox::HasValidViewBox() which checks SVGRect::IsValid (now is private and allows access from SVGFitToViewBox as a friend) and let the original callers of SVGRect::IsValid() call the new method. - Keep invalid values in SVGRect so that initial values and values set by scripts are consistent. However, if the attribute string value is invalid, the rect will be still cleared to 0,0,0,0. Bug: 1264175 Change-Id: I8aa9ecabf2055c0917bf4d66adc8400cf347c560 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3291094 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/main@{#944755} -- wpt-commits: 1da559dc43b71ae3e2e7420cddabd7ef56cdcccc wpt-pr: 31694
38d11a8a39a6ee472c0ea20ad0afe51f3922bb82: Bug 1741317 [wpt PR 31638] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 24 Nov 2021 10:34:24 +0000 - rev 600503
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1741317 [wpt PR 31638] - Update wpt metadata, a=testonly wpt-pr: 31638 wpt-type: metadata
74d47d1e7eb57cd94286b79ce96678d34b85ee36: Bug 1741317 [wpt PR 31638] - appcache: remove wpt references to appcache, a=testonly
Adrienne Walker <enne@chromium.org> - Sat, 27 Nov 2021 09:46:12 +0000 - rev 600502
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1741317 [wpt PR 31638] - appcache: remove wpt references to appcache, a=testonly Automatic update from web-platform-tests appcache: remove wpt references to appcache This is mostly a removal, but required some modifications as well. Expectations are updated to remove references to removed tests. Bug: 582750 Change-Id: I4e705f5888d3c8cd3d2cc4859a7a3816de5e88f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3283191 Commit-Queue: enne <enne@chromium.org> Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> Cr-Commit-Position: refs/heads/main@{#943332} -- wpt-commits: 561641ea142379ee9cb2531ea2ad593631868d6d wpt-pr: 31638
8ba296cd94f50b3cf85994784c96fd80439bc5e1: Bug 1742402 [wpt PR 31699] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Nov 2021 21:01:24 +0000 - rev 600501
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742402 [wpt PR 31699] - Update wpt metadata, a=testonly wpt-pr: 31699 wpt-type: metadata
dc9b2ebeebd05985d4dadf8a4fe9ad070ee09491: Bug 1742402 [wpt PR 31699] - Update webidl2.js, a=testonly
Ms2ger <Ms2ger@gmail.com> - Sat, 27 Nov 2021 09:45:49 +0000 - rev 600500
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742402 [wpt PR 31699] - Update webidl2.js, a=testonly Automatic update from web-platform-tests Update webidl2.js (#31699) -- wpt-commits: c8bd9c9b15997c24db338a372c9cba5ec823cf45 wpt-pr: 31699
239bee52e12777eb5dd5d738259ad90f97637a18: Bug 1739798 [wpt PR 31537] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 25 Nov 2021 09:36:02 +0000 - rev 600499
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1739798 [wpt PR 31537] - Update wpt metadata, a=testonly wpt-pr: 31537 wpt-type: metadata
a41356b852d2e5d3a3b50d8cd3a22900be28bb52: Bug 1739798 [wpt PR 31537] - Fix TextCodecUTF8's error handling in EOF and across buffer boundaries, a=testonly
Andreu Botella <andreu@andreubotella.com> - Sat, 27 Nov 2021 09:45:39 +0000 - rev 600498
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1739798 [wpt PR 31537] - Fix TextCodecUTF8's error handling in EOF and across buffer boundaries, a=testonly Automatic update from web-platform-tests Fix TextCodecUTF8's error handling in EOF and across buffer boundaries When TextCodecUTF8 found a truncated sequence at EOF, it used to emit one replacement character per byte in the sequence, even when it was a prefix of a valid sequence. Additionally, in streaming mode, if it found a lead byte for which a valid sequence would span longer than the current available bytes, any processing of that sequence was deferred until all such bytes were available, even if errors could be detected earlier. Both issues are solved by always checking the validity of partial sequences. The approach used in this patch uses `DecodeNonASCIISequence` to find the length of the maximal subpart of a partial sequence, and if the length is equal to the partial sequence size and we're not at EOF, we don't emit the error. However, this does not work when a byte in the 0x80 to 0xC1 range is found in a lead position, since `NonASCIISequenceLength` wrongly returns 2 and `DecodeNonASCIISequence` isn't enough to determine whether the partial sequence is invalid. This is fixed by having `NonASCIISequenceLength` to return 0 in those cases. Another issue with this approach is that, since the outer do-while loops in the `Decode` method take `do_flush && partial_sequence_size` as a condition, if a non-ASCII lead byte is found whose valid sequences would span longer than the bytes we have, those bytes would not be processed until the next call to `Decode` if `do_flush` is false. But as it turns out, the `do_flush` condition is not in fact needed, and removing it fixes this issue. Fixed: 796697 Fixed: 978522 Change-Id: Ic5a78e4eca356fdc2ad4038eba9ffe455fddf3ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3263938 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#944572} -- wpt-commits: 8e786e0fc0da2378b76a26e3dbfd96dccd8fd636 wpt-pr: 31537
785a469bf49ff0a03d2d287efd31f822fd081ded: Bug 1742157 [wpt PR 31687] - [SPC] Fixup links and one more test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Sat, 27 Nov 2021 09:45:33 +0000 - rev 600497
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742157 [wpt PR 31687] - [SPC] Fixup links and one more test, a=testonly Automatic update from web-platform-tests [SPC] Test that one cannot bypass the SPC transaction dialog -- [SPC] Fix the spec URL links for various tests -- wpt-commits: 4b49567d4c099b804143a32520247f40a145c4a9, 480b9ac4b759470542c5e8606bd06e1557ec25b4 wpt-pr: 31687
10ba5d013eb20e01b683d844abf7ecc92f33c500: Bug 1742174 [wpt PR 31690] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Nov 2021 19:14:03 +0000 - rev 600496
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742174 [wpt PR 31690] - Update wpt metadata, a=testonly wpt-pr: 31690 wpt-type: metadata
4b19001d4029a9c9f86acc2dfbd9b78dbc8015df: Bug 1742174 [wpt PR 31690] - Add WPT tests for SameSite cookies in ServiceWorkers with nested frames., a=testonly
Ben Kelly <wanderview@chromium.org> - Sat, 27 Nov 2021 09:45:20 +0000 - rev 600495
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742174 [wpt PR 31690] - Add WPT tests for SameSite cookies in ServiceWorkers with nested frames., a=testonly Automatic update from web-platform-tests Add WPT tests for SameSite cookies in ServiceWorkers with nested frames. This CL adds a number of new cases to the service worker SameSite cookies test. The cases break down into two general types: 1. Cases where A1 frames B frames A2, and then A2 calls window.open() to an A origin URL. 2. Cases where A1 frames B frames A2, and then A2 sets the location to an A origin URL. For (1) we expect SameSite strict cookies to be sent because window.open() creates a top-level context that will have a populated site-for-cookies and the initiator is same-origin (regardless of the cross-site ancestor chain). For (2) we expect only SameSite=None cookies to be sent. This is because setting the location results in a navigation to an A1->B->A3 nested frame with an empty site-for-cookies. We currently fail the passthrough and change-request cases for (2). We plan to fix this as part of storage partitioning with an ancestor chain bit in the StorageKey. See: https://github.com/privacycg/storage-partitioning/issues/25 This CL also includes some minor cleanup of the WPT test and associated resources. Bug: 1115847 Change-Id: I9002e60a271ae95d1d702068d44b30bd0e33b5dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3277058 Reviewed-by: Steven Bingler <bingler@chromium.org> Commit-Queue: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/main@{#944293} -- wpt-commits: bfe98d4bc019420281dae737739cb3982010fbc0 wpt-pr: 31690
4e8ae63a452813201fc7a67311c6b1721d84eecc: Bug 1741961 [wpt PR 31678] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Nov 2021 16:39:44 +0000 - rev 600494
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1741961 [wpt PR 31678] - Update wpt metadata, a=testonly wpt-pr: 31678 wpt-type: metadata
028590b9d5cc688132fa6299fa35354bc5329fd2: Bug 1741961 [wpt PR 31678] - Add WPT for Partitioned Service Worker claim(), a=testonly
Steven Bingler <bingler@chromium.org> - Sat, 27 Nov 2021 09:45:10 +0000 - rev 600493
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1741961 [wpt PR 31678] - Add WPT for Partitioned Service Worker claim(), a=testonly Automatic update from web-platform-tests Add WPT for Partitioned Service Worker claim() Add WPT that tests that clients.claim() is properly partitioned when storage partitioning is enabled. (For chrome) Also runs the test as part of the third-party storage partitioning virtual test suite. Bug: 1246549 Change-Id: I26f6f64ad8c1a1a531fe7503cfeb43abc99b4397 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3289538 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Ben Kelly <wanderview@chromium.org> Commit-Queue: Steven Bingler <bingler@chromium.org> Cr-Commit-Position: refs/heads/main@{#944152} -- wpt-commits: 53d10f6b8c30b04b018638eab7ac066c0ee0d03e wpt-pr: 31678
c1582c7a87119884cc72c51c1c423cc28ed1e065: Bug 1742372 [wpt PR 31697] - Remove PerLineData array in TextDecorationInfo, a=testonly
Manuel Rego Casasnovas <rego@igalia.com> - Sat, 27 Nov 2021 09:45:04 +0000 - rev 600492
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742372 [wpt PR 31697] - Remove PerLineData array in TextDecorationInfo, a=testonly Automatic update from web-platform-tests Remove PerLineData array in TextDecorationInfo We had an array for underline, overline and line-through lines in TextDecorationInfo. However as we always call SetPerLineData() and then ask for the bounds or paint the line, we don't need to store that in different positions on the array. This patch removes the array, so we have a single PerLineData in each TextDecorationInfo. Apart from that this does a few other things: * Renames PerLineData to LineData and SetPerLineData to SetLineData. * Removes the "line" argument from a bunch of methods. * Removes "line_" member from AppliedDecorationPainter as is no longer needed. Change-Id: I6cb3a95bd9eb7f7e66ad99b9b48b8bae3a1d2681 -- wpt-commits: c59f8b7441f388b92d786295bbef385a7bbbd923 wpt-pr: 31697
75c440300139794b561f456de8b1f850308e1e51: Bug 1742343 [wpt PR 31696] - SVG Text NG: Fix text layout after <svg> transform change, a=testonly
Kent Tamura <tkent@chromium.org> - Sat, 27 Nov 2021 09:44:58 +0000 - rev 600491
Push 153832 by wptsync@mozilla.com at Mon, 29 Nov 2021 19:52:02 +0000
Bug 1742343 [wpt PR 31696] - SVG Text NG: Fix text layout after <svg> transform change, a=testonly Automatic update from web-platform-tests SVG Text NG: Fix text layout after <svg> transform change If 'transform' property of the owner <svg> is changed, and <text> is painted without laying out, the content was painted at a wrong position because the <text> kept positions computed with the old scaling factor. This CL fixes it by invalidating <text> layout on 'transform' changes on the owner <svg>. This CL is similar to crrev.com/942976 but for <svg>, not for containing blocks. Bug: 1271931 Change-Id: Iefc7d9b50a8474ed536be2267ad7e5e237ed2546 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3293550 Commit-Queue: Kent Tamura <tkent@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/main@{#943987} -- wpt-commits: 10a15752e80d776d72c1caf0e0c5d433ca01ded0 wpt-pr: 31696