d6fab0c19a085278258a48eec478255461661fcf: Bug 1747334 [wpt PR 32180] - webcodecs: Move encoding web test to the external section, a=testonly
Eugene Zemtsov <eugene@chromium.org> - Mon, 10 Jan 2022 11:16:54 +0000 - rev 604176
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1747334 [wpt PR 32180] - webcodecs: Move encoding web test to the external section, a=testonly Automatic update from web-platform-tests webcodecs: Move encoding web test to the external section Also split by codec configuration to prevent timeouts and improve clarity. This CL doesn't remove old tests from the internal section, it will be done in a follow up CL. Bug: 1276335 Change-Id: I73aaec2e0bc7048fda185b467988120cc89127b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3354313 Reviewed-by: Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Cr-Commit-Position: refs/heads/main@{#955512} -- wpt-commits: 1aa39b47527284343a032317f1fc4c2f5a894aa8 wpt-pr: 32180
8c8326a5e1017f214639db0061c86bad7911f51d: Bug 1748573 [wpt PR 32242] - Update OffscreenCanvas variable name for tests, a=testonly
Yi Xu <yiyix@chromium.org> - Mon, 10 Jan 2022 11:16:48 +0000 - rev 604175
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748573 [wpt PR 32242] - Update OffscreenCanvas variable name for tests, a=testonly Automatic update from web-platform-tests Update OffscreenCanvas variable name for tests As part of the effort to unify the offscreencanvas and htmlcanvas tests, the variable names that refer to the canvas is supposed to be the same for both cases. Update all offscreencanvas variable name to canvas. Bug:1275750 Change-Id: I82b5fe5ddac366838d31e15dabd78432a2a94786 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3330901 Reviewed-by: Juanmi Huertas <juanmihd@chromium.org> Commit-Queue: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/main@{#955484} -- wpt-commits: 4f78b917b374b64d30bda6fe08d09fb3a85739e1 wpt-pr: 32242
b52226d486be1ea3b3b7a35096ab3ab4af916fac: Bug 1747817 [wpt PR 32207] - Fix the fundamental compositing bug for canvas, a=testonly
Philip Rogers <pdr@chromium.org> - Mon, 10 Jan 2022 11:09:03 +0000 - rev 604174
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1747817 [wpt PR 32207] - Fix the fundamental compositing bug for canvas, a=testonly Automatic update from web-platform-tests Fix the fundamental compositing bug for canvas Compositing should not affect the paint order of canvas. This patch changes LayoutHTMLCanvas to not force a PaintLayer, which caused canvas to draw after non-stacked siblings. PaintLayer is now primarily used for stacking contexts. A PaintLayer was previously required to support accelerated canvas. CompositeAfterPaint changed the compositing algorithm to work based on display items and property trees, rather than PaintLayer, which lets us fix this longstanding bug. The following new WPT test demonstrates the progression: wpt/css/CSS2/normal-flow/canvas-paint-order.html Bug: 370604 Change-Id: I70cbb9bb206770f5e24bbe2d2ff8ebaf0f4f6051 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3358180 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/main@{#955379} -- wpt-commits: 58168d1eb624a9262d89e80ab31832932d341568 wpt-pr: 32207
605a0f78f579110954b8e68531bac17a4e3120a8: Bug 1747166 [wpt PR 32165] - Set the androidKeepAppDataDir ChromeDriver capability for all Android browsers, a=testonly
Rakib Hasan <rmhasan@gmail.com> - Mon, 10 Jan 2022 11:08:58 +0000 - rev 604173
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1747166 [wpt PR 32165] - Set the androidKeepAppDataDir ChromeDriver capability for all Android browsers, a=testonly Automatic update from web-platform-tests Set ChromeDriver's androidKeepAppDataDir capability (#32165) This CL will make wptrunner set the androidKeepAppDataDir ChromeDriver capability for Chrome and WebLayer which will keep it from clearing out the browser's data directory. This will allow us to load browser test data into the browser's user directory. Bug: crbug.com/1233679 Co-authored-by: Rakib Hasan <rmhasan@google.com> -- wpt-commits: 38bb5f6b0ed5466470a26eebb74d5a433951dcad wpt-pr: 32165
7999b37bde2ffb4a18e5656ef80abc047b2cf56d: Bug 1748217 [wpt PR 32221] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 04 Jan 2022 14:30:30 +0000 - rev 604172
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748217 [wpt PR 32221] - Update wpt metadata, a=testonly wpt-pr: 32221 wpt-type: metadata
852c8afd56f9b630630d860872a2ee79ed2ef0c4: Bug 1748217 [wpt PR 32221] - Fix CSS gradient invalidation when currentColor changes., a=testonly
Steinar H. Gunderson <sesse@chromium.org> - Mon, 10 Jan 2022 11:08:47 +0000 - rev 604171
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748217 [wpt PR 32221] - Fix CSS gradient invalidation when currentColor changes., a=testonly Automatic update from web-platform-tests Fix CSS gradient invalidation when currentColor changes. When checking whether to invalidate an item, we check if the old and new backgrounds are “visually equal” by asking its type. However, gradients would just check that all stops are specified equally, disregarding that the old currentColor could be different from the new currentColor. Thus, add a check that if the background depends on currentColor (ie., it is a gradient that has currentColor as at least one stop), and currentColor has changed, we need to invalidate the background. Fixed: 595467 Change-Id: Ia2434aa90217352408791547f4c03a96265db909 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3353486 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Steinar H Gunderson <sesse@chromium.org> Auto-Submit: Steinar H Gunderson <sesse@chromium.org> Cr-Commit-Position: refs/heads/main@{#955109} -- wpt-commits: 38b4adf0ef3ab7ea4d114609cd46e599d7b90f60 wpt-pr: 32221
25f2d9caae720e09ab204f1675ee721c7cb801a9: Bug 1748309 [wpt PR 32230] - Don't use option style to compute combobox intrinsic size., a=testonly
Emilio Cobos Álvarez <emilio@chromium.org> - Mon, 10 Jan 2022 11:08:41 +0000 - rev 604170
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748309 [wpt PR 32230] - Don't use option style to compute combobox intrinsic size., a=testonly Automatic update from web-platform-tests Don't use option style to compute combobox intrinsic size. FIXED: 1283930 Bug: 1283930 Change-Id: I006ffe87294f497ca4e00f604d5a48ef55540320 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3365516 Auto-Submit: Emilio Cobos Álvarez <emilio@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#955071} -- wpt-commits: 91226ac86d4abe86b3179a115e93129d9f9868ef wpt-pr: 32230
194fd41df6086090a096b6b754e1aba4dd7da459: Bug 1748257 [wpt PR 32227] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Jan 2022 16:36:28 +0000 - rev 604169
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748257 [wpt PR 32227] - Update wpt metadata, a=testonly wpt-pr: 32227 wpt-type: metadata
58e943447fc2a342536fcf671305ea8c2f29b0f6: Bug 1748257 [wpt PR 32227] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=234815, a=testonly
Antti Koivisto <antti@apple.com> - Mon, 10 Jan 2022 11:08:33 +0000 - rev 604168
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748257 [wpt PR 32227] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=234815, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=234815 (#32227) -- wpt-commits: 3144d4eacf6ed505c85c8a5b4d935a0af72f02b2 wpt-pr: 32227
9065a601f6964000bddb822317b95ef4e5b0fbd1: Bug 1747266 [wpt PR 32173] - Do not allow aria-owns to parent objects with no layout, a=testonly
Aaron Leventhal <aleventhal@google.com> - Mon, 10 Jan 2022 11:08:28 +0000 - rev 604167
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1747266 [wpt PR 32173] - Do not allow aria-owns to parent objects with no layout, a=testonly Automatic update from web-platform-tests Do not allow aria-owns to parent objects with no layout If an object is unreachable by layout, it normally would not get an AXObject created for it, because it cannot have parents reaching to the root. However, aria-owns was breaking this logic, causing situations where an AXObject could be created without a legal parent. This CL adds a rule this disallows aria-owns from pointing to elements that have no layout object. While it appears to be a bit strong to disallow this, there were no clear use cases for doing it, and the rule seems to provide a useful guide rail preventing abnormal aria-owns corner cases from breaking Blink accessibility. One consideration is elements that have no layout because they use content-visibility:auto. However, these objects are recreated once they gain layout, at which time the aria-owns relationship will be valid. Fixed: 1273502,1260750 Change-Id: I48718557a9ee1805a0fdd474e688f1dcd105fe0c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3352430 Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by: Nektarios Paisios <nektar@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/main@{#955017} -- wpt-commits: fd1177c1137bc0fedc2ec8337d0261c88764f7a2 wpt-pr: 32173
8f04b759dc9f111ab5b7a4364dbc4be9801c7bd1: Bug 1748236 [wpt PR 32226] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Jan 2022 20:41:43 +0000 - rev 604166
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748236 [wpt PR 32226] - Update wpt metadata, a=testonly wpt-pr: 32226 wpt-type: metadata
db0e9995285a06a24a686b815d4b0737355f8e7c: Bug 1748236 [wpt PR 32226] - [Private Network Access] A couple more service worker WPTs., a=testonly
Titouan Rigoudy <titouan@chromium.org> - Mon, 10 Jan 2022 11:08:09 +0000 - rev 604165
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748236 [wpt PR 32226] - [Private Network Access] A couple more service worker WPTs., a=testonly Automatic update from web-platform-tests [Private Network Access] A couple more service worker WPTs. This change aligns service worker test naming and behavior with that of dedicated and shared worker tests. Bug: chromium:1239551 Change-Id: Ie2e63ad69941809bd6c0c2d8a0ec9662085c1093 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3365256 Auto-Submit: Titouan Rigoudy <titouan@chromium.org> Reviewed-by: Yifan Luo <lyf@chromium.org> Commit-Queue: Titouan Rigoudy <titouan@chromium.org> Cr-Commit-Position: refs/heads/main@{#954985} -- wpt-commits: 33849eb6578525ea9954e3a581df4bcad75389d1 wpt-pr: 32226
fa9bdb38fcce17a25d60778ad6204d004f37eb24: Bug 1748208 [wpt PR 32219] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Jan 2022 19:20:11 +0000 - rev 604164
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748208 [wpt PR 32219] - Update wpt metadata, a=testonly wpt-pr: 32219 wpt-type: metadata
e78d7a08944a80d1cc98ceb68a08f5481d76d7c6: Bug 1748208 [wpt PR 32219] - [Private Network Access] Test Worker and SharedWorker script fetches., a=testonly
Titouan Rigoudy <titouan@chromium.org> - Mon, 10 Jan 2022 11:07:53 +0000 - rev 604163
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748208 [wpt PR 32219] - [Private Network Access] Test Worker and SharedWorker script fetches., a=testonly Automatic update from web-platform-tests [Private Network Access] Test Worker and SharedWorker script fetches. It turns out that Worker fetches respect PNA when not run with PlzDedicatedWorker enabled. This makes some sense, since the scripts are fetched from within Blink using the renderer's URLLoaderFactory. When PlzDedicatedWorker is enabled however, the fetches are not subject to PNA checks, since they are performed via a URLLoaderFactory belonging to the browser process (AFAIU). This factory must be passed the correct ClientSecurityState explicitly in order for PNA checks to apply. Shared workers are in a similar state, except PlzSharedWorker is enabled by default. Bug: chromium:1282637,chromium:1282639 Change-Id: I22cd1364b6cc6b558267867480e4b22c67d78759 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3356196 Auto-Submit: Titouan Rigoudy <titouan@chromium.org> Reviewed-by: Yifan Luo <lyf@chromium.org> Commit-Queue: Yifan Luo <lyf@chromium.org> Cr-Commit-Position: refs/heads/main@{#954919} -- wpt-commits: be6d77f1f3ec5995bad868cd0f06e5ba73230647 wpt-pr: 32219
b52bbe04280c37fde72def3da0da60af68c330cb: Bug 1748209 [wpt PR 32220] - [@container] Fix incorrect shadow DOM subtests, a=testonly
Rune Lillesveen <futhark@chromium.org> - Mon, 10 Jan 2022 11:07:46 +0000 - rev 604162
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748209 [wpt PR 32220] - [@container] Fix incorrect shadow DOM subtests, a=testonly Automatic update from web-platform-tests [@container] Fix incorrect shadow DOM subtests Working on the implementation, discovered that some of the subtests were wrong. Bug: 1269192 Change-Id: I66f239dc2e30de2b2c41e2d0a98f375b80d76b71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3353449 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#954936} -- wpt-commits: 6b19cafdf4be16c27ab42fcb4d2b77e493cdf256 wpt-pr: 32220
3fb41ab13c4733037e0bd153ae9842b381eb26ef: Bug 1748225 [wpt PR 32223] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Jan 2022 18:27:48 +0000 - rev 604161
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748225 [wpt PR 32223] - Update wpt metadata, a=testonly wpt-pr: 32223 wpt-type: metadata
061ccfc9f1d8e72002a35562162dbac253028e60: Bug 1748225 [wpt PR 32223] - [Private Network Access] Test service worker registration fetches., a=testonly
Titouan Rigoudy <titouan@chromium.org> - Mon, 10 Jan 2022 11:07:38 +0000 - rev 604160
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748225 [wpt PR 32223] - [Private Network Access] Test service worker registration fetches., a=testonly Automatic update from web-platform-tests [Private Network Access] Test service worker registration fetches. Tests are currently failing because the initiator's ClientSecurityState is not correctly passed to the URLLoaderFactory used to perform the fetches from the browser process. Bug: chromium:1239551 Change-Id: I83f57ee4f1fd81f837deb51522bda71db0aab579 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3356197 Auto-Submit: Titouan Rigoudy <titouan@chromium.org> Reviewed-by: Yifan Luo <lyf@chromium.org> Commit-Queue: Yifan Luo <lyf@chromium.org> Cr-Commit-Position: refs/heads/main@{#954928} -- wpt-commits: da75a81bd7e2fdc7940eb633e644de34c366fd45 wpt-pr: 32223
88d2866b770da5a5111e2276fc4e12b7ac4ba6f0: Bug 1747658 [wpt PR 32197] - Updates css/css-color/predefined-016.html to use the new name for xyz-d50, a=testonly
Sam Weinig <weinig@apple.com> - Mon, 10 Jan 2022 11:07:33 +0000 - rev 604159
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1747658 [wpt PR 32197] - Updates css/css-color/predefined-016.html to use the new name for xyz-d50, a=testonly Automatic update from web-platform-tests Updates css/css-color/predefined-016.html to use the new name for XYZ with a D50 white point, xyz-d50, rather than the old, xyz, which now uses a D65 white point. (#32197) -- wpt-commits: e31b68f19b97c7e7040e40334f96802bf9b77f6d wpt-pr: 32197
ad7ea5db0920b773ff4ee32e80c38d46945a1908: Bug 1747659 [wpt PR 32198] - Update css/css-color/color-mix-percents-02.html to account for change in the spec to no longer allow percentages greater than 100., a=testonly
Sam Weinig <weinig@apple.com> - Mon, 10 Jan 2022 11:07:29 +0000 - rev 604158
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1747659 [wpt PR 32198] - Update css/css-color/color-mix-percents-02.html to account for change in the spec to no longer allow percentages greater than 100., a=testonly Automatic update from web-platform-tests Update color-mix-percents-02.html to no longer use percentages over 100 per spec. (#32198) The new color-mix spec doesn't allow them: https://drafts.csswg.org/css-color-5/#color-mix > Percentages are required to be in the range 0% to 100%. Negative percentages are specifically disallowed. The percentages are normalized as follows: -- wpt-commits: 177fca12c217d38688c1e96cfa7fe27f6f34ea4c wpt-pr: 32198
c34f68d7ddd114ab1b09d1d5c1427034216280b4: Bug 1748008 [wpt PR 32214] - Minor doc improvement - add 'e' to some examples, a=testonly
Andrew Williams <awillia@google.com> - Mon, 10 Jan 2022 11:07:25 +0000 - rev 604157
Push 39139 by smolnar@mozilla.com at Tue, 11 Jan 2022 21:32:55 +0000
Bug 1748008 [wpt PR 32214] - Minor doc improvement - add 'e' to some examples, a=testonly Automatic update from web-platform-tests Minor doc improvement - add 'e' to some examples -- wpt-commits: e433ff38f5230f3fec9c6fd434b942c7bffbfc67 wpt-pr: 32214
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip