0b37df7ff8eda9a8210270dd4b825c26be499673: Bug 1760722 [wpt PR 33291] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 02:14:19 +0000 - rev 687018
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760722 [wpt PR 33291] - Update wpt metadata, a=testonly wpt-pr: 33291 wpt-type: metadata
07d42e5e56e14f206a2d756aca2878e6f8162427: Bug 1760722 [wpt PR 33291] - [renderblocking] Add WPT for supported tokens of the 'blocking' attr, a=testonly
Xiaocheng Hu <xiaochengh@chromium.org> - Thu, 24 Mar 2022 12:08:50 +0000 - rev 687017
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760722 [wpt PR 33291] - [renderblocking] Add WPT for supported tokens of the 'blocking' attr, a=testonly Automatic update from web-platform-tests [renderblocking] Add WPT for supported tokens of the 'blocking' attr Bug: 1271296 Change-Id: Ief7a533569782f3bebf2496f61b870c8b1cf75f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3541559 Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org> Reviewed-by: Joey Arhar <jarhar@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#983592} -- wpt-commits: b237cd39a3acac97c2685e8f62db200a3976c0e5 wpt-pr: 33291
902b23fba31433947565a2b78421499dcf73e44c: Bug 1760771 [wpt PR 33189] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 23 Mar 2022 10:25:32 +0000 - rev 687016
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760771 [wpt PR 33189] - Update wpt metadata, a=testonly wpt-pr: 33189 wpt-type: metadata
57c05500a113b0ffc8530c4ed7c7b90da1e52d1b: Bug 1760771 [wpt PR 33189] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=237532, a=testonly
Oriol Brufau <obrufau@igalia.com> - Thu, 24 Mar 2022 12:08:41 +0000 - rev 687015
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760771 [wpt PR 33189] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=237532, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=237532 -- wpt-commits: bd29e8c5c69a5a84e0cd8d5518e80636cf0d7008 wpt-pr: 33189
c65805ee310f5fa146bea4fe09e18098e8f64e9e: Bug 1760715 [wpt PR 33232] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 11:59:53 +0000 - rev 687014
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760715 [wpt PR 33232] - Update wpt metadata, a=testonly wpt-pr: 33232 wpt-type: metadata
a18fc8ada3c45d9cacb3851a599c08ff7dbf60d5: Bug 1760715 [wpt PR 33232] - Navigation API: scrollRestoration, a=testonly
Nate Chapin <japhet@chromium.org> - Thu, 24 Mar 2022 12:08:31 +0000 - rev 687013
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760715 [wpt PR 33232] - Navigation API: scrollRestoration, a=testonly Automatic update from web-platform-tests Navigation API: scrollRestoration Explainer: https://github.com/WICG/navigation-api#scroll-position-restoration This allows a caller of NavigateEvent.transitionWhile() to specify whether or not the scroll position should be restored automatically when the navigation completes (for traverse navigations). If "scrollRestoration: 'manual'" is specified, NavigateEvent.restoreScroll() can be used any time before the navigation completes to immediately restore the scroll position. Bug: 1183545 Change-Id: I47d9d756a57854a0f42787f240f93706eb551ce1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3500700 Reviewed-by: Domenic Denicola <domenic@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/main@{#983533} -- wpt-commits: 6f1a70eb8a27133713007d06ad788527098d9f38 wpt-pr: 33232
81a084d43cc1252e195b9943bbe3c9433ba28afd: Bug 1757853 [wpt PR 33038] - Fix clicking labels for delegatesFocus form associated custom elements, a=testonly
Joey Arhar <jarhar@chromium.org> - Thu, 24 Mar 2022 12:08:20 +0000 - rev 687012
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1757853 [wpt PR 33038] - Fix clicking labels for delegatesFocus form associated custom elements, a=testonly Automatic update from web-platform-tests Fix clicking labels for delegatesFocus form associated custom elements I don't really think this behavior is well specced, but I think this behavior makes sense and it's the same as Firefox. Safari doesn't support form-associated custom elements yet. Fixed: 1300587 Change-Id: Ica4c91c7178c6c4800c3925745d1705d09e30e16 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3501331 Reviewed-by: Mason Freed <masonf@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#983491} -- wpt-commits: cc151c61d75d1107a77fc4f20f2d585a7f02fbf7 wpt-pr: 33038
908189165420aacf8a5443839b2a026d0930da89: Bug 1760684 [wpt PR 33213] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 11:46:50 +0000 - rev 687011
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760684 [wpt PR 33213] - Update wpt metadata, a=testonly wpt-pr: 33213 wpt-type: metadata
62d98c1d8196a02649417095904d107ac449fe6c: Bug 1760684 [wpt PR 33213] - [SPC] Add payeeName option, a=testonly
Nick Burris <nburris@chromium.org> - Thu, 24 Mar 2022 12:08:02 +0000 - rev 687010
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760684 [wpt PR 33213] - [SPC] Add payeeName option, a=testonly Automatic update from web-platform-tests [SPC] Add payeeName option Implementation for the recent spec change[1] to add a payeeName option as an optional alternative to payeeOrigin. The API now accepts one or both of payeeName and payeeOrigin. If both are provided, they are both shown in the UI with the format "payeeName (payeeOrigin)". This formatting when both fields are present is done in the UI code for two reasons; it's easier to test, and it can be considered a UI implementation detail how they are displayed, e.g. on a different platform or future iteration of the UI the origin could be displayed in a different font than the name, so the MVC model keeps them separate. [1] https://github.com/w3c/secure-payment-confirmation/pull/180 Bug: 1298505 Change-Id: I19a255ce9f162b7d9e6c4cf0c2164242fa96cfc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3523272 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Commit-Queue: Nick Burris <nburris@chromium.org> Cr-Commit-Position: refs/heads/main@{#983464} -- wpt-commits: 573fa63f75bbaa6940a8bfe9cb30bc06a212aae4 wpt-pr: 33213
d8f3453c8dbf45377344298cbd2e2b268c922b82: Bug 1760370 [wpt PR 33263] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 21 Mar 2022 22:51:57 +0000 - rev 687009
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760370 [wpt PR 33263] - Update wpt metadata, a=testonly wpt-pr: 33263 wpt-type: metadata
578e473b34e94b1ec3bf78920b39f8fdc572841b: Bug 1760370 [wpt PR 33263] - [FlexNG] Multi-line flex columns and margins, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 24 Mar 2022 12:07:53 +0000 - rev 687008
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760370 [wpt PR 33263] - [FlexNG] Multi-line flex columns and margins, a=testonly Automatic update from web-platform-tests [FlexNG] Multi-line flex columns and margins Add tests for margin handling and multi-line column flex containers. No extra code was needed to get this working. However, while adding tests, a bug was discovered in the iterator. If we call NextLine() while processing child break tokens, we shouldn't set next_unstarted_item_ as that will cause a DCHECK failure. Bug: 660611 Change-Id: I3fdcd558492d4c76de8c24777c0776ee3fd93ec2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3537336 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#983446} -- wpt-commits: bf875d46c851b91434045520ea722ae2b8ffd8e5 wpt-pr: 33263
556f8b5a90128c8e9f5fe5617d483303c55c5b7b: Bug 1760643 [wpt PR 33253] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 11:37:06 +0000 - rev 687007
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760643 [wpt PR 33253] - Update wpt metadata, a=testonly wpt-pr: 33253 wpt-type: metadata
1713c554436c3ccf51f609ae4b2e49152fd05e38: Bug 1760643 [wpt PR 33253] - [FlexNG] Multi-line flex columns and column balancing, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 24 Mar 2022 12:07:41 +0000 - rev 687006
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760643 [wpt PR 33253] - [FlexNG] Multi-line flex columns and column balancing, a=testonly Automatic update from web-platform-tests [FlexNG] Multi-line flex columns and column balancing There generally wasn't anything to update to get column balancing working in the case of multi-line flex columns. However, the offset adjustments we were making in the case of flex columns was still incorrect. The reason being that we were using the intrinsic block size of all columns, when we only wanted the intrinsic block size of the current column. This was fixed by moving the column intrinsic block size to NGFlexColumnBreakInfo rather than NGFlexLine so that it is reset in every fragmentainer. The calculation was also adjusted to more closely match the intrinsic_block_size_ calculation. Bug: 660611 Change-Id: I413910865ab6bab40186ced797b7b8e7863a00b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3537147 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#983383} -- wpt-commits: 3f106c52a83121f41faabef681af700825490b23 wpt-pr: 33253
54b5908db90ce92484bbfdd061b9d7858ba209cf: Bug 1760632 [wpt PR 33250] - Remove .tentative from COEP credentialless, a=testonly
Arthur Sonzogni <arthursonzogni@chromium.org> - Thu, 24 Mar 2022 12:07:32 +0000 - rev 687005
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760632 [wpt PR 33250] - Remove .tentative from COEP credentialless, a=testonly Automatic update from web-platform-tests Remove .tentative from COEP credentialless No need to use ".tentative" because the specifications have been merged into HTML and FETCH. Bug: 1175099 Change-Id: Ia82b250398eefb5fb2d022c9307e7e500b376164 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3536527 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/main@{#983352} -- wpt-commits: dba766fd6fb3494d4358a62815e74fe16d26bd31 wpt-pr: 33250
877b0d0b4555b39596c975fa7a54b8db1d382f0d: Bug 1760558 [wpt PR 33278] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 21 Mar 2022 17:57:23 +0000 - rev 687004
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760558 [wpt PR 33278] - Update wpt metadata, a=testonly wpt-pr: 33278 wpt-type: metadata
35d1f507eedd69f61c530e69c0e0625730d80059: Bug 1760558 [wpt PR 33278] - Add CSS system colors Mark and MarkText., a=testonly
Jan Keitel <jkeitel@google.com> - Thu, 24 Mar 2022 12:07:01 +0000 - rev 687003
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760558 [wpt PR 33278] - Add CSS system colors Mark and MarkText., a=testonly Automatic update from web-platform-tests Add CSS system colors Mark and MarkText. CSS Color Module Level 4 defines new system colors (https://www.w3.org/TR/css-color-4/#css-system-colors). This CL implements Mark and MarkText. Bug: 1299441 Change-Id: Id184ee58c49e7d55a32b3776e5d0d9489eb4e9cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3536909 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/main@{#983348} -- wpt-commits: 0e9eddc9d89f23d1e904e94053be6940976cd295 wpt-pr: 33278
6e29a2bed67fc44d0ecb1eeae9dad8b489ae86be: Bug 1760616 [wpt PR 33237] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 11:28:10 +0000 - rev 687002
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760616 [wpt PR 33237] - Update wpt metadata, a=testonly wpt-pr: 33237 wpt-type: metadata
c6b5268270de377300be6c06eb78df86cc7dd7e5: Bug 1760616 [wpt PR 33237] - [FlexNG] Forced break detection, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 24 Mar 2022 12:06:51 +0000 - rev 687001
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760616 [wpt PR 33237] - [FlexNG] Forced break detection, a=testonly Automatic update from web-platform-tests [FlexNG] Forced break detection We perform extra logic for forced breaks to properly handle top margins. However, we previously looked at HasForcedBreak(), which is also true if a descendant has a forced break. We only want to perform this logic if the current child break was forced. LastChildBreakToken() was added to detect this. I also noticed that we may consider an item that had previously broken before to have container separation because its previous sibling had overflow. Update the container separation logic for columns to always check if the current item previously broke. Bug: 660611 Change-Id: I08ae49dd88062afb0637f8f83be42879f774adab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3533844 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#983330} -- wpt-commits: 07201da519dd326fd7a94960cde8487a2cede780 wpt-pr: 33237
30626bb3e335724326bc1f421101037c9ec1cc9e: Bug 1760381 [wpt PR 33266] - [FlexNG] Controls DCHECK failure, a=testonly
Alison Maher <almaher@microsoft.com> - Thu, 24 Mar 2022 12:06:45 +0000 - rev 687000
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760381 [wpt PR 33266] - [FlexNG] Controls DCHECK failure, a=testonly Automatic update from web-platform-tests [FlexNG] Controls DCHECK failure We were hitting a DCHECK expecting that a button/slider was not involved in fragmentation (given that they are monolithic). However, InvolvedInBlockFragmentation() checks if an item previously broke (and monolithic content can break before). Update the check in InvolvedInBlockFragmentation() to also check that an item didn't break before previously (in which case the item hasn't (yet) been involved in fragmentation). Bug: 1277724 Change-Id: Ib4d407df05babde0ac2acfd6d0f8c4bce305cda4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3537203 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#983325} -- wpt-commits: acb2a8a93ba96e1aefda4cf85e396e6c76e6dd84 wpt-pr: 33266
6aed98d912a1fe7d267e0aa7da9f0a1fb17f1885: Bug 1760600 [wpt PR 33171] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 22 Mar 2022 11:19:41 +0000 - rev 686999
Push 2831 by ffxbld-merge at Mon, 25 Apr 2022 15:51:01 +0000
Bug 1760600 [wpt PR 33171] - Update wpt metadata, a=testonly wpt-pr: 33171 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip