searching for reviewer(testonly)
193873a769705e43125bf048e01f18ac964d91b4: Bug 1814704 - [wpt-sync] Update web-platform-tests to cfdf7a3b7129de7f29c9ff9e9d63a4cfb56696fd, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 17:56:40 +0000 - rev 651741
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814704 - [wpt-sync] Update web-platform-tests to cfdf7a3b7129de7f29c9ff9e9d63a4cfb56696fd, a=testonly MANUAL PUSH: wpt sync bot wpt-head: cfdf7a3b7129de7f29c9ff9e9d63a4cfb56696fd wpt-type: landing
839374984915fa142e1f0083f92beebbbb619774: Bug 1814413 [wpt PR 38297] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=251499, a=testonly
Antoine Quint <graouts@apple.com> - Thu, 02 Feb 2023 17:54:31 +0000 - rev 651740
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814413 [wpt PR 38297] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=251499, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=251499 (#38297) -- wpt-commits: 230dcd1d1432710630a1635f2b6c053ee0366975 wpt-pr: 38297
06d322e6d70735ed98ea75890f0d0ea611aace02: Bug 1813226 [wpt PR 38237] - [GridNG] Handle opposite writing modes in named line resolution, a=testonly
Kurt Catti-Schmidt (SCHMIDT) <kschmi@microsoft.com> - Thu, 02 Feb 2023 17:54:19 +0000 - rev 651739
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1813226 [wpt PR 38237] - [GridNG] Handle opposite writing modes in named line resolution, a=testonly Automatic update from web-platform-tests [GridNG] Handle opposite writing modes in named line resolution When named grid lines are merged, opposing writing modes from grid->subgrid should be flipped when building up the merged list. The rest of the grid layout pipeline handles the actual writing mode layout differences. This also fixes a small bug we had, where duplicated entries were not being removed from the merged list. Bug: 618969 Change-Id: If4d60e9b96078b944736e46737e9e9e5a5f423db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4195851 Reviewed-by: Ethan Jimenez <ethavar@microsoft.com> Commit-Queue: Kurt Catti-Schmidt <kschmi@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1100246} -- wpt-commits: c5a6dbc25b77dfd87907cb10332e7404ff39d0bf wpt-pr: 38237
3b7a9a6f2307e5519e0596f8b4e8a199488d1a88: Bug 1814543 [wpt PR 38314] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 03:55:48 +0000 - rev 651738
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814543 [wpt PR 38314] - Update wpt metadata, a=testonly wpt-pr: 38314 wpt-type: metadata
f64e72731bb26c74573a64ca0cfd842bb196ef87: Bug 1814543 [wpt PR 38314] - [WebCodecs] Fix broken idlharness.js test for ImageTracks, a=testonly
Dale Curtis <dalecurtis@chromium.org> - Thu, 02 Feb 2023 17:54:11 +0000 - rev 651737
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814543 [wpt PR 38314] - [WebCodecs] Fix broken idlharness.js test for ImageTracks, a=testonly Automatic update from web-platform-tests [WebCodecs] Fix broken idlharness.js test for ImageTracks The test wasn't waiting for the track list to become available before trying to inspect the tracks field. R=tguilbert Bug: 1412203 Change-Id: I18fdae6f0a8dd57531394d060d4bea24c7c8fd33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4215125 Reviewed-by: Thomas Guilbert <tguilbert@chromium.org> Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100244} -- wpt-commits: 85ebcc1f6f805d0211b72af147709d78d8a6c66c wpt-pr: 38314
5d9695a1c4d9981dd735e9184ea8eb1a40eff17a: Bug 1814060 [wpt PR 38281] - Add <input pattern> tests for RegExp `u` flag, a=testonly
Mathias Bynens <mathias@qiwi.be> - Thu, 02 Feb 2023 17:54:06 +0000 - rev 651736
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814060 [wpt PR 38281] - Add <input pattern> tests for RegExp `u` flag, a=testonly Automatic update from web-platform-tests Add <input pattern> tests for RegExp `u` flag (#38281) This patch adds a test verifying that <input pattern> is Unicode code point-aware (rather than dealing with individual surrogate halves), and another test verifying that <input pattern> supports Unicode property escape syntax. These two pieces of functionality are part of the RegExp `u` flag in JavaScript. References: - https://www.w3.org/Bugs/Public/show_bug.cgi?id=26915 - https://github.com/whatwg/html/commit/0fa713879d902d8ada81d80aa458deaf0b284b4f -- wpt-commits: e360f598f5a4c73180d2ef705195a26afb197a5d wpt-pr: 38281
15a26044008450091dd4044df8038f9a0eaaf1d1: Bug 1814505 [wpt PR 38308] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 02:17:38 +0000 - rev 651735
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814505 [wpt PR 38308] - Update wpt metadata, a=testonly wpt-pr: 38308 wpt-type: metadata
7d52658a67e2fb62f6863a4f0da3f50fdac52ba1: Bug 1814505 [wpt PR 38308] - [WebCodecs] Make CanvasHDR wpt tests internal only., a=testonly
Dale Curtis <dalecurtis@chromium.org> - Thu, 02 Feb 2023 17:53:57 +0000 - rev 651734
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814505 [wpt PR 38308] - [WebCodecs] Make CanvasHDR wpt tests internal only., a=testonly Automatic update from web-platform-tests [WebCodecs] Make CanvasHDR wpt tests internal only. CanvasHDR hasn't launched and won't for some time, so move these out of the external WPT test set. R=eugene Bug: 1274220, 1412203 Change-Id: I277b678e8798e374597170d6d6cf4bb11a3c6176 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4214580 Reviewed-by: Eugene Zemtsov <eugene@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100200} -- wpt-commits: d1192ca239e944dc6cdbcd079e1c16227e08e30c wpt-pr: 38308
716bd2a4904e12e02d4b209d243c4d343db5d349: Bug 1814523 [wpt PR 38311] - [WebCodecs] Upgrade to AVC level 3.1 for 800x600 encoding tests., a=testonly
Dale Curtis <dalecurtis@chromium.org> - Thu, 02 Feb 2023 17:53:51 +0000 - rev 651733
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814523 [wpt PR 38311] - [WebCodecs] Upgrade to AVC level 3.1 for 800x600 encoding tests., a=testonly Automatic update from web-platform-tests [WebCodecs] Upgrade to AVC level 3.1 for 800x600 encoding tests. AVC level 3.0 only supports up to 720×576 encoding, so we should be using at least 3.1 for a legal encoding. R=eugene Bug: 1412203 Change-Id: Ia69ca629950da86056fc91c1a8460b80d25f7152 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4214261 Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Reviewed-by: Eugene Zemtsov <eugene@chromium.org> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100199} -- wpt-commits: 668e382cff6963a549ce9d5af6138e68322cf431 wpt-pr: 38311
1b601c6532a8d22e650b07783c8c50a08075340b: Bug 1814541 [wpt PR 38313] - Remove elapsed time reporting in editing tests., a=testonly
Ryosuke Niwa <rniwa@webkit.org> - Thu, 02 Feb 2023 17:53:47 +0000 - rev 651732
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814541 [wpt PR 38313] - Remove elapsed time reporting in editing tests., a=testonly Automatic update from web-platform-tests Remove elapsed time reporting in editing tests. (#38313) These will vary from run to run and makes it impossible to integrate with WebKit's testing infrastructure. -- wpt-commits: 77e8ea8d86ac85632b9873c5bff56d7939a1a77f wpt-pr: 38313
7e0be6f297eb198bb421d0a59fcf187baf06b471: Bug 1814420 [wpt PR 38298] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Feb 2023 23:33:41 +0000 - rev 651731
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814420 [wpt PR 38298] - Update wpt metadata, a=testonly wpt-pr: 38298 wpt-type: metadata
423f45fd92aa1183f19aaae4ff257851159a7798: Bug 1814420 [wpt PR 38298] - Fix touch scroll up & down test for scrollend, a=testonly
Mehdi Kazemi <mehdika@chromium.org> - Thu, 02 Feb 2023 17:53:13 +0000 - rev 651730
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814420 [wpt PR 38298] - Fix touch scroll up & down test for scrollend, a=testonly Automatic update from web-platform-tests Fix touch scroll up & down test for scrollend Fix the coordinates for touch scrolling to fix the following error: "ERROR message: move target out of bounds" Also pull some of other functions to scroll_support.js to prevent code duplication. Bug: 1400447 Change-Id: I1e662c620795e3be3179b8fca0def9e4bcda8107 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4213334 Commit-Queue: Mehdi Kazemi <mehdika@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100105} -- wpt-commits: 0f4a4aeb065a012ebfdaa9e5e2638f192f77109c wpt-pr: 38298
2b2ada09d90998b38acad2349e8fef51e693c90a: Bug 1799251 [wpt PR 36831] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 09:50:49 +0000 - rev 651729
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1799251 [wpt PR 36831] - Update wpt metadata, a=testonly wpt-pr: 36831 wpt-type: metadata
0a4424f267e940cbd7868980f13cc79bb5c6edb0: Bug 1799251 [wpt PR 36831] - Implement dialog initial focus proposal, a=testonly
Joey Arhar <jarhar@chromium.org> - Thu, 02 Feb 2023 17:53:02 +0000 - rev 651728
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1799251 [wpt PR 36831] - Implement dialog initial focus proposal, a=testonly Automatic update from web-platform-tests Implement dialog initial focus proposal This has been discussed here: https://github.com/whatwg/html/pull/4184 https://github.com/whatwg/html/pull/8199 The gist of the changes are: 1. Make the dialog focusing steps look at keyboard focusable elements instead of any focusable element. 2. Make the dialog element itself get focus if it has the autofocus attribute set. 3. Make the dialog element itself get focus as a fallback instead of focus being "reset" to the body element. This patch also adds "outline:none" to several WPTs because this patch causes the dialog element to become initially focused in some cases and get a focus ring. I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/CEL3wWHrTAQ Fixed: 1193482 Change-Id: I1fee5981f72039a4467cbb35b2317832dd31bbea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3984630 Commit-Queue: Joey Arhar <jarhar@chromium.org> Reviewed-by: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100024} -- wpt-commits: 95f9b15d9aad3354f440e4e4cced5ccc405b0069 wpt-pr: 36831
8e8e16ecf1a886561cfbcf6f6805bc4eee22515e: Bug 1814474 [wpt PR 38300] - Remove unused 'scripts' parameter in WPT test generation script., a=testonly
Jean-Philippe Gravel <jpgravel@chromium.org> - Thu, 02 Feb 2023 17:52:27 +0000 - rev 651727
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814474 [wpt PR 38300] - Remove unused 'scripts' parameter in WPT test generation script., a=testonly Automatic update from web-platform-tests Remove unused 'scripts' parameter in WPT test generation script. This parameter wasn't used by any test definitions. Change-Id: Ib7dd1deec5f87eacc5fad90bbbcfd94605d14e48 Bug: 1409873 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209168 Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100036} -- wpt-commits: af3cbe44ebd705d4fd1ce82f28017b990c0ca87f wpt-pr: 38300
2962da1793a6fbace4b7f1ae3922d004c54164c6: Bug 1812897 [wpt PR 38212] - [DirectSockets] E2E support for UDP Bound mode, a=testonly
Andrew Rayskiy <greengrape@google.com> - Thu, 02 Feb 2023 17:52:18 +0000 - rev 651726
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1812897 [wpt PR 38212] - [DirectSockets] E2E support for UDP Bound mode, a=testonly Automatic update from web-platform-tests [DirectSockets] E2E support for UDP Bound mode This CL provides the missing blocks for end-to-end UDP Bound mode: (*) Extends UDPSocketOptions to accept localAddress and (optional) localPort inside UDPSocket constructor in udp_socket.idl (*) Adds new params to DirectUDPSocketOptions and teaches OpenUDPSocket() to handle bound mode requests on the browser side. Change-Id: I400fed2fb22c751d8b2e5cae5c33b277c27fdf44 Bug: 1404938 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4189446 Commit-Queue: Andrew Rayskiy <greengrape@google.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100020} -- wpt-commits: 5f01d1710ce86fbf56465e01c4f2e2021d3822e7 wpt-pr: 38212
66df03caba5d4c8094e7aea3e89c0f16950f0303: Bug 1813941 [wpt PR 38271] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 09:20:50 +0000 - rev 651725
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1813941 [wpt PR 38271] - Update wpt metadata, a=testonly wpt-pr: 38271 wpt-type: metadata
4cd5445115d8083698e6f7b77fddc9fb94bc5d54: Bug 1813941 [wpt PR 38271] - Add slot=marker and ::part(marker) for selectmenu, a=testonly
Joey Arhar <jarhar@chromium.org> - Thu, 02 Feb 2023 17:52:10 +0000 - rev 651724
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1813941 [wpt PR 38271] - Add slot=marker and ::part(marker) for selectmenu, a=testonly Automatic update from web-platform-tests Add slot=marker and ::part(marker) for selectmenu Fixed: 1357866 Change-Id: I98cd880837e37ebad3e178ff8382ecc490a9313d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4206659 Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1100000} -- wpt-commits: 801440028c5887105541f29eebdbf6352915e05f wpt-pr: 38271
7609ae4ec5c47801641edcadd3c8a8664a79b4f2: Bug 1812482 [wpt PR 38181] - Add FilterOptions to performance.getEntries() behind a flag, a=testonly
Hao Liu <haoliuk@chromium.org> - Thu, 02 Feb 2023 17:51:56 +0000 - rev 651723
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1812482 [wpt PR 38181] - Add FilterOptions to performance.getEntries() behind a flag, a=testonly Automatic update from web-platform-tests Add FilterOptions to performance.getEntries() behind a flag This CL adds a new GetEntries(FilterOptions options) API. The FilterOptions consists of name, entryType and includeChildFrames on which performance entries can be filtered. The CL also removes the optional argument includeFrames from GetEntries, GetEntriesByName and GetEntriesByType. Change-Id: Ib4dcdba95268d873b86ce1dbd3a30ef29d09f5e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4188992 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Hao Liu <haoliuk@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099995} -- wpt-commits: 531d5a41a2be1a32ee9ba2891d079752b4500dfe wpt-pr: 38181
703572a88589ce166e20cc3c5065ad3627aea04e: Bug 1812670 [wpt PR 38202] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 09:18:37 +0000 - rev 651722
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1812670 [wpt PR 38202] - Update wpt metadata, a=testonly wpt-pr: 38202 wpt-type: metadata
68a7ef0d262c7b75610f7ed69e7402bf42cf335d: Bug 1812670 [wpt PR 38202] - Fix storage bucket quota overflow, a=testonly
Nathan Memmott <memmott@chromium.org> - Thu, 02 Feb 2023 17:51:41 +0000 - rev 651721
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1812670 [wpt PR 38202] - Fix storage bucket quota overflow, a=testonly Automatic update from web-platform-tests Fix storage bucket quota overflow This fixes overflow and underflow issues with storage buckets. Creating a bucket with a quota 2^31 or greater would cause the bucket's quota to overflow when stored in the quota database. A negative number would overflow the other way when processed by v8. This updates all variables representing quota to signed int64s to match how it is represented in the database. It also adds the EnforceRange attribute to the idl, so that it automatically errors when out of range (-(2^53) to 2^53-1). This also adds checks for negative quotas and errors if there is one. Bug: 1406355 Change-Id: I5ba8d7716e8ec9735b2da453ff3e6a90e47211e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4171741 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Nathan Memmott <memmott@chromium.org> Reviewed-by: Nathan Memmott <memmott@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099984} -- wpt-commits: 6e081c8b5b9ff1e60b56c3005b1476f79e0f64e9 wpt-pr: 38202
07b9fab8130b12e0e5764c17936a10ef108946f0: Bug 1814466 [wpt PR 38299] - Simplify the code writing canvas WPT test files., a=testonly
Jean-Philippe Gravel <jpgravel@chromium.org> - Thu, 02 Feb 2023 17:51:37 +0000 - rev 651720
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1814466 [wpt PR 38299] - Simplify the code writing canvas WPT test files., a=testonly Automatic update from web-platform-tests Simplify the code writing canvas WPT test files. This will be useful in follow-up CLs, where more logic will be added here. Change-Id: I1ef0542ed8e6c6f4757f1edbcd7f1352fd186ebc Bug: 1409873 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209088 Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099967} -- wpt-commits: 0f9ac04696ad69dd1977b341ce5aca394aecdd8a wpt-pr: 38299
0ac2bc1724d41c09c3437be96dd8552c26400be4: Bug 1812008 [wpt PR 38135] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 02 Feb 2023 09:14:56 +0000 - rev 651719
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1812008 [wpt PR 38135] - Update wpt metadata, a=testonly wpt-pr: 38135 wpt-type: metadata
8c054e217905e700e0fe7f75742f628d67abda97: Bug 1812008 [wpt PR 38135] - WPT: Rename assertBFCache to assertBFCacheEligibility, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Thu, 02 Feb 2023 17:50:59 +0000 - rev 651718
Push 40602 by abutkovits@mozilla.com at Sat, 04 Feb 2023 09:11:16 +0000
Bug 1812008 [wpt PR 38135] - WPT: Rename assertBFCache to assertBFCacheEligibility, a=testonly Automatic update from web-platform-tests WPT: Rename assertBFCache to assertBFCacheEligibility (#38135) The original name sounds too ambiguous, as we are adding more assertion helper functions, it's better to give it a more accurate name. This CL also rename `assert_not_bfcached` to `assertNotRestoredFromBFCache` and `assert_implements_bfcache` to `assertImplementsBFCacheOptional`. Bug: 1408436 Change-Id: I80daaccb894d853b17818103a416255df0af431e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4179422 Commit-Queue: Mingyu Lei <leimy@chromium.org> Reviewed-by: Yuzu Saijo <yuzus@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099160} Co-authored-by: Mingyu Lei <leimy@chromium.org> -- wpt-commits: 21a947094fad8273dca9524ef3d35c876a26b1c7 wpt-pr: 38135
994397e1439d290c537bfaea5ee0c3f3f67e4599: Bug 1814515 - [wpt-sync] Update web-platform-tests to 1d842727e128cd23f894f8ec05ef78f0e37452f3, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Feb 2023 22:37:21 +0000 - rev 651531
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814515 - [wpt-sync] Update web-platform-tests to 1d842727e128cd23f894f8ec05ef78f0e37452f3, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 1d842727e128cd23f894f8ec05ef78f0e37452f3 wpt-type: landing
d5cf7f1b19750b708749d201f7829aea2b0e7416: Bug 1814106 [wpt PR 38286] - Make the canvas size parameterizable in generated WPT tests., a=testonly
Jean-Philippe Gravel <jpgravel@chromium.org> - Wed, 01 Feb 2023 22:33:53 +0000 - rev 651530
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814106 [wpt PR 38286] - Make the canvas size parameterizable in generated WPT tests., a=testonly Automatic update from web-platform-tests Make the canvas size parameterizable in generated WPT tests. Right now, the "canvas" template parameter was used for both specifying custom attributes for the canvas tag, but also for specifying the size. Having dedicated parameters for the canvas size makes it possible to customize the size for both element and and offscreen tests. Bug: 1409873 Change-Id: I63a550d90871f25a9dcc00a2b4f6ceff5c916d34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4208909 Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099918} -- wpt-commits: 1d842727e128cd23f894f8ec05ef78f0e37452f3 wpt-pr: 38286
81f98e2275cfc56ab84adf3d661fabc2d4fb0a57: Bug 1814336 [wpt PR 38294] - [MediaCapture Extensions] Fire configurationchange event conditionally, a=testonly
François Beaufort <beaufort.francois@gmail.com> - Wed, 01 Feb 2023 22:33:42 +0000 - rev 651529
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814336 [wpt PR 38294] - [MediaCapture Extensions] Fire configurationchange event conditionally, a=testonly Automatic update from web-platform-tests [MediaCapture Extensions] Fire configurationchange event conditionally This CL makes sure the MediaStreamTrack configuration event is fired if the background blur capabilities and settings from the image capture photo state have changed. Spec: https://w3c.github.io/mediacapture-extensions/#exposing-change-of-mediastreamtrack-configuration Bug: 1409011 Change-Id: I3d6c6e14cce9c1330c45439f9ac5849424023724 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4180612 Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Fr <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/main@{#1099838} -- wpt-commits: 56cf3d3d267a1fd713f6ea1623228ef8a03c7521 wpt-pr: 38294
552a4466f63b9b071f9fa3e96fe3a39305e21ab2: Bug 1813504 [wpt PR 38251] - Image Capture: Supply unsupported constraint name in error message, a=testonly
François Beaufort <beaufort.francois@gmail.com> - Wed, 01 Feb 2023 22:33:37 +0000 - rev 651528
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813504 [wpt PR 38251] - Image Capture: Supply unsupported constraint name in error message, a=testonly Automatic update from web-platform-tests Image Capture: Supply unsupported constraint name in error message This CL makes sure the name of the unsupported constraint is provided when applyConstraints() returned promise rejects. Bug: 1408091 Change-Id: I7346dc998864682cca553624286eb2d24c119a61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4197606 Reviewed-by: Eero Hakkinen <eero.hakkinen@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Fr <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/main@{#1099805} -- wpt-commits: 2b5668ac25e1495b8c3e3cbc5d8bfa22be28e0e7 wpt-pr: 38251
25d734e6a9a4974de0cdf14358437a3e3a40b504: Bug 1814380 [wpt PR 38295] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Feb 2023 16:00:28 +0000 - rev 651527
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814380 [wpt PR 38295] - Update wpt metadata, a=testonly wpt-pr: 38295 wpt-type: metadata
b947301cfb02f7d95a4365ea069c421072d62ab6: Bug 1814380 [wpt PR 38295] - Registered custom property initial value tests for style() queries, a=testonly
Rune Lillesveen <futhark@chromium.org> - Wed, 01 Feb 2023 22:33:28 +0000 - rev 651526
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814380 [wpt PR 38295] - Registered custom property initial value tests for style() queries, a=testonly Automatic update from web-platform-tests Registered custom property initial value tests for style() queries Bug: 1302630 Change-Id: I77d08c5556c94892a0fbe2cd2304894b8ec3c8b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4210416 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099778} -- wpt-commits: 5f3dfa1a3508bc5093d8358d40a5f031f4df7ec7 wpt-pr: 38295
3f156a14bcc003801b5f17e04bac8bc2b388589a: Bug 1811773 [wpt PR 38100] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Feb 2023 09:16:42 +0000 - rev 651525
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1811773 [wpt PR 38100] - Update wpt metadata, a=testonly wpt-pr: 38100 wpt-type: metadata
0d4d494de50554b11aabec8fc6ed60418cdf7726: Bug 1811773 [wpt PR 38100] - [webnn] Add float32 tests for WebNN convTranspose2d op., a=testonly
BruceDai <feng.dai@intel.com> - Wed, 01 Feb 2023 22:33:19 +0000 - rev 651524
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1811773 [wpt PR 38100] - [webnn] Add float32 tests for WebNN convTranspose2d op., a=testonly Automatic update from web-platform-tests [webnn] Add float32 tests for WebNN convTranspose2d op. (#38100) * [webnn] Add float32 tests for WebNN convTranspose2d op. * [webnn] Support float32 convTranspose2d tests with filter as constant operand. * [webnn] Fix coding style issues. -- wpt-commits: 071f6833861c96a29f4ab90aef9cee1c85d6c8a7 wpt-pr: 38100
809932dd228f8b91f77f3172a2c541173538ae29: Bug 1814265 [wpt PR 38290] - Corrected ch-units-vrl-006 test according to Issue 36378, a=testonly
Gérard Talbot <github@gtalbot.org> - Wed, 01 Feb 2023 22:33:08 +0000 - rev 651523
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814265 [wpt PR 38290] - Corrected ch-units-vrl-006 test according to Issue 36378, a=testonly Automatic update from web-platform-tests Corrected ch-units-vrl-006 test according to Issue 36378 -- wpt-commits: 82bb58565898d1d78a03cb136d7142ac44955de3 wpt-pr: 38290
6c3ca2d00bdf73a39ece82a28c1bdac93bb47265: Bug 1812479 [wpt PR 38179] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 01 Feb 2023 01:38:41 +0000 - rev 651522
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1812479 [wpt PR 38179] - Update wpt metadata, a=testonly wpt-pr: 38179 wpt-type: metadata
586cdadde66e2d544811339939378cba7f2385c4: Bug 1812479 [wpt PR 38179] - navigation.navigate(url, { history: "push" }); should actually force push, a=testonly
Nate Chapin <japhet@chromium.org> - Wed, 01 Feb 2023 22:32:49 +0000 - rev 651521
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1812479 [wpt PR 38179] - navigation.navigate(url, { history: "push" }); should actually force push, a=testonly Automatic update from web-platform-tests navigation.navigate(url, { history: "push" }); should actually force push Currently, { history: "push" } is actually push-or-fail: if the navigation would've been a push, it pushes. If it would've been a replace, the navigation fails immediately. This CL makes { history: "push" } actually override some cases where we would implicitly convert a push navigation to a replace: navigations before onload completes, and navigation to the current url. Change-Id: I0b985a4c9563c6000f7ee44153394466cc4bcb50 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4175895 Reviewed-by: Rakina Zata Amni <rakina@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Owners-Override: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099590} -- wpt-commits: 3a5a9aff54b708f2778832a5781af9f6ea4ba928 wpt-pr: 38179
f942d0cc34de44265d08230cb85a6e912de0811a: Bug 1813926 [wpt PR 38270] - Check if an object is in a locked display before executing update., a=testonly
Yotam Hacohen <yotha@chromium.org> - Wed, 01 Feb 2023 22:32:42 +0000 - rev 651520
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813926 [wpt PR 38270] - Check if an object is in a locked display before executing update., a=testonly Automatic update from web-platform-tests Check if an object is in a locked display before executing update. When we walk the tree in pre-paint, we stop the walk for children of an object with locked display. This patch adds a similar check to the deferred updates that are executed separately after the walk. Bug: 1407382 Change-Id: I00c8b73eab7d9101882f264191d25f04c8158cb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4189343 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Yotam Hacohen <yotha@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099548} -- wpt-commits: d80a211a093ebb8289e2c8ef5f9520167fb3b0a4 wpt-pr: 38270
70f9dc6d80948f5223db539709b21650f2e6874e: Bug 1814085 [wpt PR 38285] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 31 Jan 2023 22:02:26 +0000 - rev 651519
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814085 [wpt PR 38285] - Update wpt metadata, a=testonly wpt-pr: 38285 wpt-type: metadata
bdb9e0fdce4ab870dd7ca2a86f28ad1d3e52912a: Bug 1814085 [wpt PR 38285] - Fix for repeated table sections inside clipped container., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Wed, 01 Feb 2023 22:32:33 +0000 - rev 651518
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814085 [wpt PR 38285] - Fix for repeated table sections inside clipped container., a=testonly Automatic update from web-platform-tests Fix for repeated table sections inside clipped container. When we reach the block-end of a container with clipped overflow, we re-lay out the last fragment with block fragmentation forced off. That's RelayoutWithoutFragmentation() in NGLayoutAlgorithm. In this mode we didn't handle repeated table sections correctly. First of all, we wouldn't detect that the sections were repeatable at all, because IsAvoidBreakValue() would return false, since the constraint space says that we're not inside any block fragmentation (and therefore break-inside:avoid should have no effect). Move that check into code that's only run when at the first table box fragment. Secondly, we were bypassing some code that was needed to detect that we need to RelayoutAsLastTableBox() at this point. Fix that as well. We could perhaps have set the is_known_to_be_last_table_box_ in NGTableLayoutAlgorithm instead when in RelayoutWithoutFragmentation, but fixing it this way instead seemed more robust, less convoluted, albeit a bit more expensive, since we're performing an unnecessary layout pass at the last table fragment (but that should really be no big deal). Bug: 1410896 Change-Id: If63da5a7388bc7dbc70681195c079b9cbe03907e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4208191 Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099436} -- wpt-commits: 3e17a57f7c5376d3d0a0512747c0f4d8317d1d48 wpt-pr: 38285
27a03a548e13228127aa7c7c182dd31a0c059563: Bug 1814233 [wpt PR 38289] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 31 Jan 2023 22:04:46 +0000 - rev 651517
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814233 [wpt PR 38289] - Update wpt metadata, a=testonly wpt-pr: 38289 wpt-type: metadata
b66df59c8e2816bf73702d5685a5cdf83bd014e8: Bug 1814233 [wpt PR 38289] - FSA: Fix create-sync-access-handle test flakiness, a=testonly
Austin Sullivan <asully@chromium.org> - Wed, 01 Feb 2023 22:32:10 +0000 - rev 651516
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814233 [wpt PR 38289] - FSA: Fix create-sync-access-handle test flakiness, a=testonly Automatic update from web-platform-tests FSA: Fix create-sync-access-handle test flakiness Replaces a file_system_type variable (which was not always defined at the time the script runs with a getFileSystemType() method that's implemented by both the local and sandboxed test helpers. --gtest_repeat=100 shows no failures, whereas before this change it was ~6 failures per 100 Fixed: 1409178 Change-Id: I50fa8fab2bfcc5b60df29701e0a3018fddbe21c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4209261 Commit-Queue: Daseul Lee <dslee@chromium.org> Auto-Submit: Austin Sullivan <asully@chromium.org> Reviewed-by: Daseul Lee <dslee@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099424} -- wpt-commits: fd37d07189e3997496ca53dca82e4ffd7e45531e wpt-pr: 38289
2238d5d77d361d7cfa2515d6149cfbcb8047fcf1: Bug 1813718 [wpt PR 38263] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 31 Jan 2023 21:25:03 +0000 - rev 651515
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813718 [wpt PR 38263] - Update wpt metadata, a=testonly wpt-pr: 38263 wpt-type: metadata
caa70443fa7ba4f7c76912d2bae7a424e949730a: Bug 1813718 [wpt PR 38263] - [view-timeline] Support range(Start|End) as strings in animation options., a=testonly
Kevin Ellis <kevers@google.com> - Wed, 01 Feb 2023 22:31:59 +0000 - rev 651514
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813718 [wpt PR 38263] - [view-timeline] Support range(Start|End) as strings in animation options., a=testonly Automatic update from web-platform-tests [view-timeline] Support range(Start|End) as strings in animation options. This patch also extends length support to handle style dependent units. Remaining step: Update style-dependent lengths. Bug: 1407923 Change-Id: Iad81e8caac695905538b8c63b6c80fe6203a473b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4198530 Commit-Queue: Kevin Ellis <kevers@chromium.org> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099413} -- wpt-commits: 2be285c4590f27c0dc0ea51e9290a6f4d4c44596 wpt-pr: 38263
8c55e14ba3aa6ef08cf95e654f267792d10d1eef: Bug 1813876 [wpt PR 38269] - Reland "Update popover post-toggle event naming and behavior", a=testonly
Mason Freed <masonf@chromium.org> - Wed, 01 Feb 2023 22:31:46 +0000 - rev 651513
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813876 [wpt PR 38269] - Reland "Update popover post-toggle event naming and behavior", a=testonly Automatic update from web-platform-tests Reland "Update popover post-toggle event naming and behavior" This is a reland of commit 2e5ee120d7fc5df4b6c101e88d03a5f62a73d8b8 It seems that the event coalescing behavior changes cause a segfault in the event dispatch code. This reland (compare to Patchset 1) just includes the event renaming, and not the new behavior. I'll land the new behavior in a separate CL to make it smaller if it gets reverted again. This part should be safe. Original change's description: > Update popover post-toggle event naming and behavior > > This CL updates the post-toggle event in the following ways: > 1. Rename the 'aftertoggle' event to 'toggle'. > 2. Rename PopoverToggleEvent to ToggleEvent. > 3. Rename the currentState attribute to oldState. > 4. Add event coalescing behavior. If two transitions occur before the > first 'toggle' event has been fired, cancel the first event and > queue a replacement that has oldState === newState. > > These changes were driven by the corresponding changes to the spec PR: > https://github.com/whatwg/html/pull/8717 > > Bug: 1307772 > Change-Id: Iabc5a9093d7cef3bbd6e54e488d8e571c51ea568 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4195120 > Auto-Submit: Mason Freed <masonf@chromium.org> > Commit-Queue: Joey Arhar <jarhar@chromium.org> > Reviewed-by: Joey Arhar <jarhar@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1098728} Bug: 1307772 Change-Id: Iede18bbf05516cec4ee881f1afc663c45380c82e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4205710 Reviewed-by: Joey Arhar <jarhar@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099397} -- wpt-commits: 1effa5f2e38566fde9acd65c6a92a08cc0d830c3 wpt-pr: 38269
8190b62323c5690a6581754d54c04f1ef51c53ab: Bug 1813965 [wpt PR 38275] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 31 Jan 2023 20:05:26 +0000 - rev 651512
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813965 [wpt PR 38275] - Update wpt metadata, a=testonly wpt-pr: 38275 wpt-type: metadata
95944849f2aa3fe985637cbddc0d8074a9de6b9b: Bug 1813965 [wpt PR 38275] - Image Loading: Remove `last_base_element_url_`, a=testonly
Dominic Farolino <dom@chromium.org> - Wed, 01 Feb 2023 22:31:35 +0000 - rev 651511
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813965 [wpt PR 38275] - Image Loading: Remove `last_base_element_url_`, a=testonly Automatic update from web-platform-tests Image Loading: Remove `last_base_element_url_` `blink::ImageLoader::last_base_element_url_` stores a snapshot of the Document's base URL during UpdateFromElement() [1]. However, this snapshot is not actually used to resolve the URL of the image request after the microtask checkpoint in DoUpdateFromElement(); rather, relative URL resolution always happens with the Document's live base URL mechanism [2] (more on this later). Instead, the member exists solely to detect, at image insertion time [3], if the Document's base URL has changed since the last time UpdateFromElement() was called. The rationale for this used to be to detect if a document's base URL changed before the image loading microtask (DoUpdateFromElement()) was run, so that we could protect against fetching the wrong image with a stale URL; see [4]. This was important because at the time, (before crrev.com/c/2103987) ImageLoader used to store a snapshot of the resolved image URL in the microtask state computed in UpdateFromElement(), so it was possible to wind up in DoUpdateFromElement() with an image request URL that is stale compared to the live Document's base URL (this was intentional, see crbug.com/569760 & https://codereview.chromium.org/2105283002). The solution [5] at the time was to detect, only during insertion, if the ImageLoader's last known snapshot of the Document base URL is stale, so that the image processing model can be re-entered, and the final DoUpdateFromElement() call is made with an up-to-date URL. This protects against the very specific issue of: 1. Creating an image (thus scheduling the microtask) 2. Changing the Document's base URL 3. The microtask that finally runs fetches an image with a stale URL However, I have no idea how this could protect against the original bug filed [4]; see https://chromium-review.googlesource.com/c/chromium/src/+/3311225/comments/5ab9c13f_9c553169 where there is some discussion about how the original bug could have behaved. In any case, since then, crrev.com/c/2103987 has landed which ensures that DoUpdateElement() always resolves relative URLs with the live Document's base URL, so it is impossible for DoUpdateElement() to fetch an outdated URL. This leaves us with the `last_base_element_url_` member that is used as a discriminator to re-invoke the image processing model upon insertion due to this member being stale compared to the Document's base URL. This results in Chromium sometimes fetching the same exact image twice (3-step scenario listed above), which makes this member entirely obsolete dead weight. Furthermore, the HTML Standard does not define general image insertion as a "relevant mutation" [6] that would invoke #update-the-image-data, and it certainly does not capture any base-URL-specific state in the microtask machinery. After some discussion on https://github.com/whatwg/html/issues/7383, we've decided to align Chromium with the specification, which prompts this CL. Testing-wise, this CL is covered by: - image-load-reset-on-new-base.html - Created in response to [4] - svg-image-load-reset-on-new-base.html - Same as above, but the SVG variant - image-base-url.html - Added/moved in crrev.com/c/2103987 - TODO: Add a test that ensures only one request is made - This test is important because while the others ensure that the final image is correct, we've discovered that some browsers are re-fetching the image due to base URLs changing before the image microtask is run, and sometimes that second fetch is using the correct URL, and sometimes it's wrong: https://github.com/whatwg/html/issues/7383#issuecomment-1408234538 [1]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/loader/image_loader.cc;l=646-647;drc=3297fb6d70a02d8c4af8db2bc9e315053744442b [2]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/loader/image_loader.cc;l=724;drc=3297fb6d70a02d8c4af8db2bc9e315053744442b [3]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/loader/image_loader.cc;l=297-302;drc=3297fb6d70a02d8c4af8db2bc9e315053744442b [4]: https://crbug.com/897545 [5]: https://crrev.com/c/1296506 [6]: https://html.spec.whatwg.org/multipage/images.html#relevant-mutations Bug: 569760,897545 Change-Id: If6a93c091bfaea2944489e3660adc695d04c3e72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3311225 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099380} -- wpt-commits: 05e83c2ea5c6ccd05517d8b788e6b547976b7961 wpt-pr: 38275
f7b170ca65c962a0d86d09c2b7cc222c63888c76: Bug 1814073 [wpt PR 38282] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=251433, a=testonly
Antoine Quint <graouts@apple.com> - Wed, 01 Feb 2023 22:31:30 +0000 - rev 651510
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1814073 [wpt PR 38282] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=251433, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=251433 (#38282) -- wpt-commits: ae74e9c26b40d0b81a137b7a7d1004b078ee3e93 wpt-pr: 38282
c72a3c497cede5d6fee697f1b021bbbc310510fe: Bug 1811015 [wpt PR 38038] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 31 Jan 2023 18:41:40 +0000 - rev 651509
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1811015 [wpt PR 38038] - Update wpt metadata, a=testonly wpt-pr: 38038 wpt-type: metadata
fcc5d97146e086c6aa64b4f02fa1b90eec135811: Bug 1811015 [wpt PR 38038] - WPT: Create function to test BFCache not restored reason, a=testonly
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> - Wed, 01 Feb 2023 22:31:13 +0000 - rev 651508
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1811015 [wpt PR 38038] - WPT: Create function to test BFCache not restored reason, a=testonly Automatic update from web-platform-tests WPT: Create function to test BFCache not restored reason (#38038) Added a function `assertBFCacheNotRestoredReasonsIfApplicable` that uses the `notRestoredReasons` API. Unlike the helper functions in performance timing API folder, this one only checks the main frame's reasons, which should be good (and concise) enough for most of the BFCache feature WPTs. If the API is not available, the function will return straightaway instead report assertion failure. This CL also modifies back-forward-cache-open-connection.window.js as an example usage of the helper function. Bug: 1408436 Change-Id: Ia6215ae88bc295b9c2d8c164aab78780ded3606c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4177970 Reviewed-by: Fergal Daly <fergal@chromium.org> Reviewed-by: Yuzu Saijo <yuzus@chromium.org> Commit-Queue: Mingyu Lei <leimy@chromium.org> Cr-Commit-Position: refs/heads/main@{#1098432} Co-authored-by: Mingyu Lei <leimy@chromium.org> -- wpt-commits: 5362f7c50698409e80e0b7f06ebc79c049ef3886 wpt-pr: 38038
d7b0b1644803e3e7d68e801fecdf89f8b4a99d5d: Bug 1813528 [wpt PR 38255] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 31 Jan 2023 15:53:57 +0000 - rev 651507
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813528 [wpt PR 38255] - Update wpt metadata, a=testonly wpt-pr: 38255 wpt-type: metadata
737e021837abc101ebbf790fcfe827f01ebc84c6: Bug 1813528 [wpt PR 38255] - [css-nesting] Keep nest-containing invalid selectors within :is()., a=testonly
Steinar H. Gunderson <sesse@chromium.org> - Wed, 01 Feb 2023 22:30:46 +0000 - rev 651506
Push 40598 by nerli@mozilla.com at Thu, 02 Feb 2023 17:20:03 +0000
Bug 1813528 [wpt PR 38255] - [css-nesting] Keep nest-containing invalid selectors within :is()., a=testonly Automatic update from web-platform-tests [css-nesting] Keep nest-containing invalid selectors within :is(). See https://github.com/w3c/csswg-drafts/issues/7972. Bug: 1095675 Change-Id: Ifebb6e8d2f4a2c0f627abaea4a432173a0993f01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4203527 Commit-Queue: Steinar H Gunderson <sesse@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1099231} -- wpt-commits: bbb24b5a2d4b3a1f959b12e6b1377758feb0a50e wpt-pr: 38255