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 674267
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +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 674266
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +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 674265
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +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
b112d0625e0d947317f50c0eece987317ca9f14d: Bug 1742166 [wpt PR 31689] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 24 Nov 2021 09:52:55 +0000 - rev 674264
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742166 [wpt PR 31689] - Update wpt metadata, a=testonly wpt-pr: 31689 wpt-type: metadata
cb7d9c6a7f9a1ebcbd5a95d713db8ca3f4cc99e8: Bug 1742166 [wpt PR 31689] - Fix SameSite WPT window.open() tests, a=testonly
Steven Bingler <bingler@chromium.org> - Sat, 27 Nov 2021 09:44:49 +0000 - rev 674263
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742166 [wpt PR 31689] - Fix SameSite WPT window.open() tests, a=testonly Automatic update from web-platform-tests Fix SameSite WPT window.open() tests These two tests had a typo in which the `origin` was used as the start and the target of the test navigations. The `target` argument was unused. This CL corrects that and updates the expected results for a couple affected tests. (Plus some comments changes.) Change-Id: I913f927c755ef21f2c6632bc84fca7b624a894a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3290927 Reviewed-by: Mike Taylor <miketaylr@chromium.org> Commit-Queue: Steven Bingler <bingler@chromium.org> Cr-Commit-Position: refs/heads/main@{#943722} -- wpt-commits: 295ea9766d034fe2cf4a18832ea3eca448689012 wpt-pr: 31689
2196d59098de64b89455db49a57638c49a6db339: Bug 1715886 [wpt PR 29334] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Nov 2021 16:06:05 +0000 - rev 674262
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1715886 [wpt PR 29334] - Update wpt metadata, a=testonly wpt-pr: 29334 wpt-type: metadata
a9a97484bf319312462aa8894a45a5d5671d81d5: Bug 1715886 [wpt PR 29334] - Change behavior of window.open w.r.t. windowPreferences and popups, a=testonly
Mason Freed <masonf@chromium.org> - Sat, 27 Nov 2021 09:44:40 +0000 - rev 674261
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1715886 [wpt PR 29334] - Change behavior of window.open w.r.t. windowPreferences and popups, a=testonly Automatic update from web-platform-tests Change behavior of window.open w.r.t. windowPreferences and popups See [1] and [2] for more context, but this CL implements new behavior for how window.open() interprets the windowPreferences argument when deciding whether to open the window as a new tab or as a "popup", which is a separate window with minimal UI (toolbars, onmibox, etc.), and also what to return from the BarProp visible properties, e.g. window.toolbar.visible. The existing "trigger" behavior for popups will be retained by this CL, namely that a popup will be opened instead of a tab if: 1. the windowFeatures parameter is *not* empty, and 2. one of the following conditions is true: * both `location` and `toolbar` are false or missing * `menubar` is false or missing * `resizable is false or missing * `scrollbar` is false or missing * `status` is false or missing With this CL, an additional windowFeature called 'popup' is added, so that if 'popup' is present and truthy. Additionally, all BarProp properties (locationbar,menubar, personalbar,scrollbars,statusbar, and toolbar) will always return the same values, either false if a popup was opened, or true if a tab/window was opened. The spec for this behavior is part of the HTML spec: https://html.spec.whatwg.org/multipage/window-object.html#popup-window-is-requested The intent to ship is here: https://groups.google.com/a/chromium.org/g/blink-dev/c/q6ybnmxxvpE [1] https://github.com/whatwg/html/issues/5872 [2] https://github.com/whatwg/html/pull/6530 Fixed: 1192701 Change-Id: I50e745b1000d460c49085edd57d13f420b875ff3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2950386 Reviewed-by: Joey Arhar <jarhar@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#943716} -- wpt-commits: 3660b77d3cec8138401c12e055bee44d62e9b060 wpt-pr: 29334
a280ea92b24a05e6739677e4b126059a9eab845a: Bug 1742486 [wpt PR 31706] - [Timers] Make evil-spec-example.html an any.js test, a=testonly
Andreu Botella <abb@randomunok.com> - Sat, 27 Nov 2021 09:44:35 +0000 - rev 674260
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742486 [wpt PR 31706] - [Timers] Make evil-spec-example.html an any.js test, a=testonly Automatic update from web-platform-tests [Timers] Make evil-spec-example.html an any.js test (#31706) Co-authored-by: Anne van Kesteren <annevk@annevk.nl> -- wpt-commits: e554f36b099f03317cfb1207ef4edc0486dcbaf5 wpt-pr: 31706
58707b9017a32c783dd095b4a492ef9d6771ef56: Bug 1742399 [wpt PR 31698] - Test that `clearInterval` works inside the interval's callback, a=testonly
Andreu Botella <abb@randomunok.com> - Sat, 27 Nov 2021 09:44:29 +0000 - rev 674259
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742399 [wpt PR 31698] - Test that `clearInterval` works inside the interval's callback, a=testonly Automatic update from web-platform-tests Test that `clearInterval` works inside the interval's callback (#31698) Ref: whatwg/html#7356 -- wpt-commits: 2948653c47c2d84d14fbac0706d2b86ada41323a wpt-pr: 31698
d0b923beaf2c6940c0c4103dc763c06757450354: Bug 1742452 [wpt PR 31705] - Fix invalidation bug for <select> caret style, a=testonly
Mason Freed <masonf@chromium.org> - Sat, 27 Nov 2021 09:44:24 +0000 - rev 674258
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742452 [wpt PR 31705] - Fix invalidation bug for <select> caret style, a=testonly Automatic update from web-platform-tests Fix invalidation bug for <select> caret style Previously, setting the color (or likely other styles?) for a <select> after it was initially rendered would not result in an updated rendering of the caret. Fixed: 1269840 Change-Id: Iee971dea8beda969d1e40cbd2886ce05bd330f17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3292448 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/main@{#944372} -- wpt-commits: 5797f8279721042f4beb16f03ae52677c91e1460 wpt-pr: 31705
3515020ec386528559b151f43234b56aab7adc0c: Bug 1742165 [wpt PR 31688] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 24 Nov 2021 09:51:37 +0000 - rev 674257
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742165 [wpt PR 31688] - Update wpt metadata, a=testonly wpt-pr: 31688 wpt-type: metadata
c789ea3e46af73b3a225f713fb9afc23312bb38a: Bug 1742165 [wpt PR 31688] - Update [video-]dynamic-range media queries, a=testonly
Will Cassella <cassew@chromium.org> - Sat, 27 Nov 2021 09:44:15 +0000 - rev 674256
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742165 [wpt PR 31688] - Update [video-]dynamic-range media queries, a=testonly Automatic update from web-platform-tests Update [video-]dynamic-range media queries As of the latest discussion on the spec, it's been determined that '[video-]dynamic-range: standard' should be a subset of '[video-]dynamic-range: high'. This CL implements that change, and updates all tests accordingly. The relevant spec discussion may be viewed here: https://github.com/w3c/csswg-drafts/issues/6793 Bug: 1224711 Change-Id: I640e574cd2809dc1d8b721115e79372d302c723a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3293745 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Will Cassella <cassew@chromium.org> Cr-Commit-Position: refs/heads/main@{#944203} -- wpt-commits: 166dd2ceeaecb1e22ecf7c5c08713a47cf828deb wpt-pr: 31688
dc2ca63454abe124206a276a4a60dc7524b3441e: Bug 1742451 [wpt PR 31704] - Fix WPT title, a=testonly
Mason Freed <masonf@chromium.org> - Sat, 27 Nov 2021 09:44:10 +0000 - rev 674255
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1742451 [wpt PR 31704] - Fix WPT title, a=testonly Automatic update from web-platform-tests Fix WPT title No functional changes. Change-Id: I05087b6a64de33ee21b26c7146b48424c9337eeb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3296326 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/main@{#944179} -- wpt-commits: 2858bee631d799c8b7e7f1d42833a7cfcbab11c0 wpt-pr: 31704
f9db9bf6b2793f7a11064e4f07dcd4515d357f17: Bug 1740642 [wpt PR 31592] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 24 Nov 2021 10:13:54 +0000 - rev 674254
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1740642 [wpt PR 31592] - Update wpt metadata, a=testonly wpt-pr: 31592 wpt-type: metadata
29f349b181b61e0ef4d6e0017096904e61fab880: Bug 1740642 [wpt PR 31592] - Highlight API: Add test coverage, a=testonly
Fernando Fiori <ffiori@microsoft.com> - Sat, 27 Nov 2021 09:44:00 +0000 - rev 674253
Push 2724 by ffxbld-merge at Mon, 03 Jan 2022 22:10:59 +0000
Bug 1740642 [wpt PR 31592] - Highlight API: Add test coverage, a=testonly Automatic update from web-platform-tests Highlight API: Add test coverage These tests are meant to verify that: - UAs must not define any styles for custom highlight pseudo-elements in the default UA stylesheet. - A custom highlight pseudo-element inherits the styles of its originating element. See https://drafts.csswg.org/css-highlight-api-1/#default-styles Bug: 1164461 Change-Id: I955f39ee185fe2282d7599c07ff1cdd7df2d7059 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3273351 Commit-Queue: Fernando Fiori <ffiori@microsoft.com> Reviewed-by: Dan Clark <daniec@microsoft.com> Cr-Commit-Position: refs/heads/main@{#944166} -- wpt-commits: d19addc73e13b8b3bc98bc51262bb0e42418eece wpt-pr: 31592
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 +10000 tip