Bug 1729169 - [wpt-sync] Update web-platform-tests to 4a8e1e081701c95a7f2d27eff2d2a9ee96691edc, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 4a8e1e081701c95a7f2d27eff2d2a9ee96691edc wpt-type: landing

Bug 1728654 [wpt PR 30290] - URLPattern: Support constructor strings with ipv6 addresses., a=testonly Automatic update from web-platform-tests URLPattern: Support constructor strings with ipv6 addresses. This adds support for constructor strings like: new URLPattern("http://[\\:\\:1]/"); As discussed in spec issue #113: https://github.com/WICG/urlpattern/issues/113 Fixed: 1245760 Change-Id: I712341e72a5c2af745dbbdbb8673a79809a98425 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138336 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#917682} -- wpt-commits: 4a8e1e081701c95a7f2d27eff2d2a9ee96691edc wpt-pr: 30290

Bug 1728628 [wpt PR 30287] - Update wpt metadata, a=testonly wpt-pr: 30287 wpt-type: metadata

Bug 1728628 [wpt PR 30287] - Fix test picture generation and add test., a=testonly Automatic update from web-platform-tests Fix test picture generation and add test. (#30287) This CL changes the test picture from a growing box to a small moving box. It adds a test that the expected bandwidth target is achieved at the expected resolution. In a browser, 640x480 is not reached within 5 seconds. This is odd. Bug: None. Change-Id: I2d94f1c190c26cec6759ecc0f788feea8e52ed7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3135833 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/main@{#917211} Co-authored-by: Harald Alvestrand <hta@chromium.org> -- wpt-commits: fb595c54c13e1dc40b9f8e68016079164114e8fd wpt-pr: 30287

Bug 1728343 [wpt PR 30257] - Reland "Populate pointerId, pointerType for contextmenu event", a=testonly Automatic update from web-platform-tests Reland "Populate pointerId, pointerType for contextmenu event" This is a second reland of a6d69d5243dd02afbd8ef02e5a5c557dd8c4a9e9 I believe the reason for the test failures when this landed the first time was related to how pointerId was populated for the contextmenu pointer event. With crrev.com/c/2889205 landed, we have a robust way to associate the gesture event sequence with the corresponding pointer event sequence. This CL uses the approach in crrev.com/c/2889205 to populate the pointerId for the contextmenu pointer event. The reason this didn't reland at first, is because there is a difference between the gesture sequences generated by run_web_tests.py and wpt runner. See crbug.com/1245118. Until crbug.com/1245118 is fixed, I am adding an expectation file for chrome. The other reason this didn't reland at first, is because the test pointerevent_contextmenu_is_a_pointerevent.html?touch is flaky on Mac. I am going to add it back to TestExpectations, and try to land the TestExpectations file change separately from this CL. Original change's description: > Populate pointerId, pointerType for contextmenu event > > For contextmenu as a pointer event pointerId and pointerType > were not populated. > > In this CL we are populating pointerId/pointerType for contextmenu > coming from touch and mouse. > For touch we use a similar approach to crrev.com/c/2800231 > for populating pointerId,pointerType for clicks generated in > GestureManager::HandleGestureTap. > The main change will be in EventHandler::SendContextMenuEvent > where we'll be passing id and pointer type to the call to > MouseEventManager::DispatchMouseEvent. This in turn will > populate pointerId and pointerType correctly when the contextmenu > PointerEvent is created. > > Bug: 1150442,1150441 > TEST: external/wpt/pointerevents/pointerevent_contextmenu_is_a_pointerevent.html > Change-Id: If2408d9cf0d5f00b08efcf2236ff7933472972ce > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2874026 > Commit-Queue: Liviu Tinta <liviutinta@chromium.org> > Reviewed-by: Robert Flack <flackr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#881145} Bug: 1150442,1150441,1207709,626703 Change-Id: I84cd65f80be00fa7a09c8248039c95ec05a2e1fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3132060 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Cr-Commit-Position: refs/heads/main@{#917671} -- wpt-commits: 69a086eab1e1b4d01c815b5e2b6cb75a30d8571f wpt-pr: 30257

Bug 1728673 [wpt PR 30292] - [ResourceTiming]: Update resource_cached.html to follow the new style, a=testonly Automatic update from web-platform-tests [ResourceTiming]: Update resource_cached.html to follow the new style This change updates the named test to conform to the new style described in wpt/resource-timing/CodingConventions.md. GithubIssue: https://github.com/w3c/resource-timing/issues/254 Bug: 1171767 Change-Id: Iba63250828c33df477852aeddd1b1e1cf49f88c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138593 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/main@{#917665} -- wpt-commits: 9888b4153005f30dc493eddcb50fa800a24c3d7f wpt-pr: 30292

Bug 1728150 [wpt PR 30232] - [SPC] WPT tests for payment extension in get-assertion, a=testonly Automatic update from web-platform-tests [SPC] WPT tests for payment extension in get-assertion Changes: * adds the WPT tests for payment extensions in get-assertion. * guards get()'s payment extension error with the SPC flag. Bug: 1243479 Change-Id: Iab892fd506ecd928c270f9c4916ccd7c3512d501 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3130460 Reviewed-by: Nina Satragno <nsatragno@chromium.org> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/main@{#917664} -- wpt-commits: eb42fd53ab8f94b6c2302eecd39e1faa25b3d7fd wpt-pr: 30232

Bug 1729130 - [wpt-sync] Update web-platform-tests to 4a8e1e081701c95a7f2d27eff2d2a9ee96691edc, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 4a8e1e081701c95a7f2d27eff2d2a9ee96691edc wpt-type: landing

Bug 1728654 [wpt PR 30290] - URLPattern: Support constructor strings with ipv6 addresses., a=testonly Automatic update from web-platform-tests URLPattern: Support constructor strings with ipv6 addresses. This adds support for constructor strings like: new URLPattern("http://[\\:\\:1]/"); As discussed in spec issue #113: https://github.com/WICG/urlpattern/issues/113 Fixed: 1245760 Change-Id: I712341e72a5c2af745dbbdbb8673a79809a98425 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138336 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#917682} -- wpt-commits: 4a8e1e081701c95a7f2d27eff2d2a9ee96691edc wpt-pr: 30290

Bug 1728628 [wpt PR 30287] - Update wpt metadata, a=testonly wpt-pr: 30287 wpt-type: metadata

Bug 1728628 [wpt PR 30287] - Fix test picture generation and add test., a=testonly Automatic update from web-platform-tests Fix test picture generation and add test. (#30287) This CL changes the test picture from a growing box to a small moving box. It adds a test that the expected bandwidth target is achieved at the expected resolution. In a browser, 640x480 is not reached within 5 seconds. This is odd. Bug: None. Change-Id: I2d94f1c190c26cec6759ecc0f788feea8e52ed7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3135833 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/main@{#917211} Co-authored-by: Harald Alvestrand <hta@chromium.org> -- wpt-commits: fb595c54c13e1dc40b9f8e68016079164114e8fd wpt-pr: 30287

Bug 1728343 [wpt PR 30257] - Reland "Populate pointerId, pointerType for contextmenu event", a=testonly Automatic update from web-platform-tests Reland "Populate pointerId, pointerType for contextmenu event" This is a second reland of a6d69d5243dd02afbd8ef02e5a5c557dd8c4a9e9 I believe the reason for the test failures when this landed the first time was related to how pointerId was populated for the contextmenu pointer event. With crrev.com/c/2889205 landed, we have a robust way to associate the gesture event sequence with the corresponding pointer event sequence. This CL uses the approach in crrev.com/c/2889205 to populate the pointerId for the contextmenu pointer event. The reason this didn't reland at first, is because there is a difference between the gesture sequences generated by run_web_tests.py and wpt runner. See crbug.com/1245118. Until crbug.com/1245118 is fixed, I am adding an expectation file for chrome. The other reason this didn't reland at first, is because the test pointerevent_contextmenu_is_a_pointerevent.html?touch is flaky on Mac. I am going to add it back to TestExpectations, and try to land the TestExpectations file change separately from this CL. Original change's description: > Populate pointerId, pointerType for contextmenu event > > For contextmenu as a pointer event pointerId and pointerType > were not populated. > > In this CL we are populating pointerId/pointerType for contextmenu > coming from touch and mouse. > For touch we use a similar approach to crrev.com/c/2800231 > for populating pointerId,pointerType for clicks generated in > GestureManager::HandleGestureTap. > The main change will be in EventHandler::SendContextMenuEvent > where we'll be passing id and pointer type to the call to > MouseEventManager::DispatchMouseEvent. This in turn will > populate pointerId and pointerType correctly when the contextmenu > PointerEvent is created. > > Bug: 1150442,1150441 > TEST: external/wpt/pointerevents/pointerevent_contextmenu_is_a_pointerevent.html > Change-Id: If2408d9cf0d5f00b08efcf2236ff7933472972ce > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2874026 > Commit-Queue: Liviu Tinta <liviutinta@chromium.org> > Reviewed-by: Robert Flack <flackr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#881145} Bug: 1150442,1150441,1207709,626703 Change-Id: I84cd65f80be00fa7a09c8248039c95ec05a2e1fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3132060 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Cr-Commit-Position: refs/heads/main@{#917671} -- wpt-commits: 69a086eab1e1b4d01c815b5e2b6cb75a30d8571f wpt-pr: 30257

Bug 1728673 [wpt PR 30292] - [ResourceTiming]: Update resource_cached.html to follow the new style, a=testonly Automatic update from web-platform-tests [ResourceTiming]: Update resource_cached.html to follow the new style This change updates the named test to conform to the new style described in wpt/resource-timing/CodingConventions.md. GithubIssue: https://github.com/w3c/resource-timing/issues/254 Bug: 1171767 Change-Id: Iba63250828c33df477852aeddd1b1e1cf49f88c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138593 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/main@{#917665} -- wpt-commits: 9888b4153005f30dc493eddcb50fa800a24c3d7f wpt-pr: 30292

Bug 1728150 [wpt PR 30232] - [SPC] WPT tests for payment extension in get-assertion, a=testonly Automatic update from web-platform-tests [SPC] WPT tests for payment extension in get-assertion Changes: * adds the WPT tests for payment extensions in get-assertion. * guards get()'s payment extension error with the SPC flag. Bug: 1243479 Change-Id: Iab892fd506ecd928c270f9c4916ccd7c3512d501 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3130460 Reviewed-by: Nina Satragno <nsatragno@chromium.org> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/main@{#917664} -- wpt-commits: eb42fd53ab8f94b6c2302eecd39e1faa25b3d7fd wpt-pr: 30232

Bug 1728936 - [wpt-sync] Update web-platform-tests to 2af53e681fe37f5b9f0f8d02ad3d60c95437821f, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 2af53e681fe37f5b9f0f8d02ad3d60c95437821f wpt-type: landing

Bug 1728758 [wpt PR 30302] - Fix DCHECK failure on aborted response, a=testonly Automatic update from web-platform-tests Fix DCHECK failure on aborted response We need to check the AbortSignal status before starting loading. Bug: 1245439 Change-Id: I3f4a43e8acbb6c2f77d3839367866365cabe08d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3139723 Reviewed-by: Adam Rice <ricea@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/main@{#917657} -- wpt-commits: 2af53e681fe37f5b9f0f8d02ad3d60c95437821f wpt-pr: 30302

Bug 1728694 [wpt PR 30296] - [ResourceTiming]: Fix incorrect for-loop iteration, a=testonly Automatic update from web-platform-tests [ResourceTiming]: Fix incorrect for-loop iteration We were using `for (const [key, value] in Object.entries(thingy))` but that iterates the indices of the array returned by Object.entries We need to use `for (const [key, value] of Object.entries(thingy))` to get (key, value) pairs instead of (index,`undefined`) pairs. Bug: 1171767 Change-Id: I81848afe8dc31dced5363476a1367ce353f8a02a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138594 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/main@{#917636} -- wpt-commits: 778ac9655ae8dd6976501429e641fa2096e88665 wpt-pr: 30296

Bug 1728288 [wpt PR 30255] - Fix bad payments test, a=testonly Automatic update from web-platform-tests Fix bad payments test (#30255) -- wpt-commits: 15994385e7413ae5e6248d0d1113f77a314a6371 wpt-pr: 30255

Bug 1721560 [wpt PR 29727] - Update wpt metadata, a=testonly wpt-pr: 29727 wpt-type: metadata

Bug 1721560 [wpt PR 29727] - Add Webtransport over HTTP/3 test server, a=testonly Automatic update from web-platform-tests Add Webtransport over HTTP/3 test server (#29727) -- wpt-commits: 1903175e1e7241a16da454f69c1c62ba00963a4e wpt-pr: 29727

Bug 1728523 [wpt PR 30281] - Update wpt metadata, a=testonly wpt-pr: 30281 wpt-type: metadata

Bug 1728523 [wpt PR 30281] - Add Content-Security-Policy WPTs for WebTransport, a=testonly Automatic update from web-platform-tests Add Content-Security-Policy WPTs for WebTransport This CL adds two test cases: - when connect-src is set to none, the WebTransport connection fails - when connect-src is set to the page destination, the WebTransport connection is established successfully Furthermore, the custom-reponse server handler is also added in this CL, which will be used in some follow-up CLs to respond to CONNECT requests. The test expectations have also been updated in this CL, by skipping these WebTransport WPTs for the timebeing until the server is added. Bug: 1201569 Change-Id: I4c0c1b947751e71accda69682769c3f461c7fb6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3134999 Commit-Queue: Nidhi Jaju <nidhijaju@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/main@{#917597} -- wpt-commits: 679b01b186186215fdd3cbdb54039d8a31b8bc15 wpt-pr: 30281

Bug 1728722 [wpt PR 30299] - Update wpt metadata, a=testonly wpt-pr: 30299 wpt-type: metadata

Bug 1728722 [wpt PR 30299] - Cascade layer @import tests, a=testonly Automatic update from web-platform-tests Cascade layer @import tests (#30299) * Cascade layer @import tests * Update css/css-cascade/layer-import.html Co-authored-by: Tim Nguyen <nt1m@users.noreply.github.com> Co-authored-by: Tim Nguyen <nt1m@users.noreply.github.com> -- wpt-commits: aa53a501b570ccdea56a1e1435e361a4eb8c5131 wpt-pr: 30299

Bug 1728209 [wpt PR 30239] - Update wpt metadata, a=testonly wpt-pr: 30239 wpt-type: metadata

Bug 1728209 [wpt PR 30239] - [wasm] Deprecate cross-origin module sharing, a=testonly Automatic update from web-platform-tests [wasm] Deprecate cross-origin module sharing With this CL cross-origin module sharing gets disabled by default. It can be re-enabled by setting the command line switch `cross-origin-webassembly-module-sharing-allowed`, by setting the enterprise policy `CrossOriginWebAssemblyModuleSharingEnabled`, or by --enable-features=CrossOriginWebAssemblyModuleSharingEnabled. Bug: chromium:1225641 Change-Id: I950f2121856a8c185df93e27c476ec90faf3f136 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3094205 Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Anqing Zhao <anqing@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#917573} -- wpt-commits: cd381d102622e91faf515ab77f8ca0376fbaf311 wpt-pr: 30239

Bug 1728733 [wpt PR 30258] - Update wpt metadata, a=testonly wpt-pr: 30258 wpt-type: metadata

Bug 1728733 [wpt PR 30258] - Implement font-synthesis-style functionality, a=testonly Automatic update from web-platform-tests Implement font-synthesis-style functionality Implement of CSS property font-synthesis-style functionality, which controls synthesized oblique. Added tests for web and system fonts. Added helper methods that check if synthetic bold and italic are allowed. Bug: 509989 Change-Id: I2ebc55370626158230b7a8255aeb065a5fc2eea2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128025 Reviewed-by: Dominik Röttsches <drott@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#917571} -- wpt-commits: 617ff01ccd64a0ec94812bb2f8a2134e864cdf24 wpt-pr: 30258

Bug 1728678 [wpt PR 30293] - Update wpt metadata, a=testonly wpt-pr: 30293 wpt-type: metadata

Bug 1728678 [wpt PR 30293] - Add test for ImageCapture.takePhoto() setOptions failure, a=testonly Automatic update from web-platform-tests Add test for ImageCapture.takePhoto() setOptions failure This change is a follow-up to crrev.com/c/3132384 which adds a new Web Platform Test that reproduces the issue by calling takePhoto() on a stream which doesn't provide PhotoCapabilities. Bug: 1229991 Change-Id: I685c587915587edf2573e182658d84de637171e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3138862 Auto-Submit: Reilly Grant <reillyg@chromium.org> Reviewed-by: Yuki Shiino <yukishiino@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/main@{#917528} -- wpt-commits: 37bce9094cbec3cc3b69832925808f5a7811913e wpt-pr: 30293

Bug 1728481 [wpt PR 30278] - Update wpt metadata, a=testonly wpt-pr: 30278 wpt-type: metadata

Bug 1728481 [wpt PR 30278] - [LayoutNG] HasBlockFragmentation() -> InvolvedInBlockFragmentation(), a=testonly Automatic update from web-platform-tests [LayoutNG] HasBlockFragmentation() -> InvolvedInBlockFragmentation() Similar to CL:2843465, update the checks from HasBlockFragmentation() to InvolvedInBlockFragmentation() before calling FinishFragmentation() in the fieldset and multicol layout algorithms. Bug: 829028 Change-Id: I5f5e4601ae0db524b03d9e2cccad115cdc9c791e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3134312 Commit-Queue: Alison Maher <almaher@microsoft.com> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#917312} -- wpt-commits: 6df4ea72da452abcbc0075b81957bbc962a462e2 wpt-pr: 30278

Bug 1728480 [wpt PR 30277] - Update wpt metadata, a=testonly wpt-pr: 30277 wpt-type: metadata

Bug 1728480 [wpt PR 30277] - [ResourceTiming]: Update iframe-failed-commit.html WPT, a=testonly Automatic update from web-platform-tests [ResourceTiming]: Update iframe-failed-commit.html WPT This change updates wpt/resource-timing/iframe-failed-commit.html to conform to the new style guidelines in wpt/resource-timing/CodingConventions.md. GithubIssue: https://github.com/w3c/resource-timing/issues/254 Bug: 1171767 Change-Id: Ica54e4ea7fe9ae74bb1fa4274c803297577face8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3134283 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/main@{#917277} -- wpt-commits: f3d3029b18e579c83ee09a5dccb7adbba9cd47d8 wpt-pr: 30277

Bug 1722841 [wpt PR 29834] - Add support for relative URLs in Subresource Loading from WebBundles., a=testonly Automatic update from web-platform-tests Add support for relative URLs in Subresource Loading from WebBundles. When using a 'resources' attribute in the <link> element with WebBundles we only use absolute URLs to said resources. This change makes it so we can use relative URLs instead and resolve them with the page's base URL. <base> element can cause a dynamic change in the base URL, which we should support. This will be done in a follow-up CL. Bug: 1213335, 1244483 Change-Id: I6a2169ba697c102208f7488eef2debc8674cba7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059820 Commit-Queue: Miras Myrzakerey <myrzakereyms@google.com> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/main@{#917201} -- wpt-commits: 539f10ded71c181492ebbea454d22162f5e85635 wpt-pr: 29834

Bug 1727154 [wpt PR 30128] - Add manual WPT for file handling., a=testonly Automatic update from web-platform-tests Add manual WPT for file handling. (#30128) Note that to test this in Chrome with run_blink_wptserve.py, Chrome must be started with: --ignore-certificate-errors --enable-features=FileHandlingAPI Bug: 1240389 Change-Id: I9462a48fa8c69beb596c23ecec878c262fad3027 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3114865 Reviewed-by: Joshua Bell <jsbell@chromium.org> Reviewed-by: Daniel Murphy <dmurph@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/main@{#915261} Co-authored-by: Evan Stade <estade@chromium.org> -- wpt-commits: 42a57900ee61b9b10d81952c8c6ff3d3d096eccf wpt-pr: 30128

Bug 1728088 [wpt PR 30226] - Update wpt metadata, a=testonly wpt-pr: 30226 wpt-type: metadata

Bug 1728088 [wpt PR 30226] - Increase bandwidth of fake video signal used for testing., a=testonly Automatic update from web-platform-tests Increase bandwidth of fake video signal used for testing. (#30226) This will increase the size of an encoded 640x480 video from approximately 8 Kbits/second to approximately 64 Kbits/second, which means that limiting the bandwidth will actually have an effect. This is done in preparation for further tests that limit the bandwidth and expect an observable result. Bug: None Change-Id: Ib3c63c4ae8c41fe7c608f1c06c8c61c2beecbe11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3128063 Reviewed-by: Florent Castelli <orphis@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/main@{#916377} Co-authored-by: Harald Alvestrand <hta@chromium.org> -- wpt-commits: ed9b278329b48455b62195b32be8aa0f40812de5 wpt-pr: 30226

Bug 1728570 [wpt PR 30286] - Replace forced-break-in-nested-columns.html with a correct WPT test., a=testonly Automatic update from web-platform-tests Replace forced-break-in-nested-columns.html with a correct WPT test. The old test was assuming a legacy engine implementation limitation, where we're unable to push the first fragment of a multicol container to the next outer fragmentainer if there was no room for its contents in the current outer fragmentainer. In the test, see the first DIV child of the inner .mc. The legacy engine would just push the line inside that DIV to the next outer fragmentainer, even if there's no valid breakpoint there. The correct behavior is to push the first fragment of the inner multicol container itself to the next outer fragmentainer (there's a perfect breakpoint after the first DIV child of the outer .mc. LayoutNG block fragmentation gets this right. Bug: 829028 Change-Id: I55950c5aad3418b49dabe12debd43317cf578c96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3135656 Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#917263} -- wpt-commits: 48655d84e0d96d6bfe1ce0446a291f3379f1e5ff wpt-pr: 30286

Bug 1728248 [wpt PR 30248] - [webid] Expose WebID as an extension of the Credential Manager API., a=testonly Automatic update from web-platform-tests [webid] Expose WebID as an extension of the Credential Manager API. Overloads FederatedCredential adding new attributes as well as static methods to support the mediated of the Account Chooser for FederatedCredentials. Explainer: https://github.com/WICG/WebID I2P https://groups.google.com/a/chromium.org/g/blink-dev/c/2B4TJ7j2U4M Spec Draft: https://wicg.github.io/WebID Change-Id: I2176ea4e687b9ac3fe7387e5658cf5c4adcfc6b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3123775 Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Commit-Queue: Sam Goto <goto@chromium.org> Cr-Commit-Position: refs/heads/main@{#917241} -- wpt-commits: 04ffcc174898cbb842ebd4a9d8751ac40ae432a9 wpt-pr: 30248

Bug 1728581 - [wpt-sync] Update web-platform-tests to a5b0a22fff9949b9e755f1ca628b6fb4509f93c1, a=testonly MANUAL PUSH: wpt sync bot wpt-head: a5b0a22fff9949b9e755f1ca628b6fb4509f93c1 wpt-type: landing

Bug 1728227 [wpt PR 30245] - Bump pytest from 6.2.4 to 6.2.5 in /tools, a=testonly Automatic update from web-platform-tests Bump pytest from 6.2.4 to 6.2.5 in /tools Bumps [pytest](https://github.com/pytest-dev/pytest) from 6.2.4 to 6.2.5. - [Release notes](https://github.com/pytest-dev/pytest/releases) - [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst) - [Commits](https://github.com/pytest-dev/pytest/compare/6.2.4...6.2.5) --- updated-dependencies: - dependency-name: pytest dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> -- wpt-commits: a5b0a22fff9949b9e755f1ca628b6fb4509f93c1 wpt-pr: 30245

Bug 1728485 [wpt PR 30203] - URLPattern: Fix matched values for ':name*' patterns., a=testonly Automatic update from web-platform-tests URLPattern: Fix matched values for ':name*' patterns. This fixes the problem where: const p = new URLPattern({ pathname: ':name*' }); const r = p.exec('foobar'); console.log(r.pathname.groups.name); Would log 'r' instead of 'foobar'. This is an upstream bug in path-to-regexp as well: https://github.com/pillarjs/path-to-regexp/issues/260 Fixed: 1243773 Change-Id: I402d2b8cba48386d9ae02a493068488a7ad91d70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3123654 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#917069} -- wpt-commits: 72cebca780a3165482da11103f28b4fb4752aed4 wpt-pr: 30203

Bug 1727546 [wpt PR 30176] - Paint background images correctly with LayoutNGBlockFragmentation., a=testonly Automatic update from web-platform-tests Paint background images correctly with LayoutNGBlockFragmentation. Bug: 1200242 Change-Id: I130d7a4e69453f835343ac7e171c76c0956a6b3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3113939 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#915476} -- Add CSS-COLLIDING-REF-NAME to lint ignore -- wpt-commits: ae30763027da340929f6f6569cdf7c4ee67bafbd, 1aa215c9bef50e1cabda969423c836f87f04ef80 wpt-pr: 30176

Bug 1728451 [wpt PR 30272] - Lazyload: Lazyload images can load from the list of available images, a=testonly Automatic update from web-platform-tests Lazyload: Lazyload images can load from the list of available images As per step 6 in #updating-the-image-data [1], all images including lazyloaded ones are able to load immediately from the list of available images. This CL adds a test ensuring this is the case, specifically for out-of-viewport `loading=lazy` images. If it is determined in https://github.com/whatwg/html/issues/7005 that even in-flight requests are able to be placed in the list of available images, this would increase the utility of the list of available images, and maximize the number of requests that can "coalesce" with entries in said list. In that case, we'll need to: 1.) Correct the tentative expectations introduced in crrev.com/c/3133524 2.) Write a test specifically for lazyload to verify that lazyloaded images don't have special behavior, and can indeed coalesce with in-flight requests in the list of available images [1]: https://html.spec.whatwg.org/multipage/images.html#updating-the-image-data:list-of-available-images R=domenic@chromium.org Bug: 994329 Change-Id: I511c09073226f729782c47cc135d36efd2ef4723 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3133207 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#917059} -- wpt-commits: 57c7282839049b334bd96aa6cc7e336b2dfae558 wpt-pr: 30272

Bug 1728447 [wpt PR 30271] - URLPattern: Test that bad URL inputs to match routines return failure., a=testonly Automatic update from web-platform-tests URLPattern: Test that bad URL inputs to match routines return failure. This adds coverage for the following code: https://analysis.chromium.org/p/chromium/coverage/file?host=chromium.googlesource.com&project=chromium/src&ref=refs/heads/main&revision=399808806081f555cc4b4ca60821c9efc9a9ac04&path=//third_party/blink/renderer/modules/url_pattern/url_pattern.cc&platform=linux&test_suite_type=any#490 Bug: 1245067 Change-Id: Ic42f9a82452866c034df00064ff074c288227401 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3133612 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#917045} -- wpt-commits: c472b505c61ab279a3d28079fa0a5c40fe3ba600 wpt-pr: 30271

Bug 1728381 [wpt PR 30260] - Update wpt metadata, a=testonly wpt-pr: 30260 wpt-type: metadata

Bug 1728381 [wpt PR 30260] - IndexedDB: Fix readyState() check failure, a=testonly Automatic update from web-platform-tests IndexedDB: Fix readyState() check failure The existing DCHECK is incorrect, since readyState() can be called with ready_state_ == kEarlyDeath if the accessor is hit after the execution context is destroyed. Bug: 1243946 Change-Id: Ia5a56b232b8c9e9d2ca142fb1c487286aa22f77b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3125334 Commit-Queue: Austin Sullivan <asully@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#917017} -- wpt-commits: f2d65ccfcbba84619aba2dd6e559ed70ef6bf63d wpt-pr: 30260

Bug 1728359 [wpt PR 30259] - Update wpt metadata, a=testonly wpt-pr: 30259 wpt-type: metadata

Bug 1728359 [wpt PR 30259] - Images: Add test for list of available image coalescing, a=testonly Automatic update from web-platform-tests Images: Add test for list of available image coalescing This CL adds a test ensuring that the list of available images is not used to coalesce an image request into a current in-flight request The HTML Standard's list of available images [1] is only added to once all of of the bytes of an image have been fetched, and the `load` event is about to be fired [2]. This means that if an image request A is currently in-flight, and an image request B is made for the exact same image, both requests should hit the network and not be coalesced. This is also explicitly the intention of the spec: "It is not used to avoid re-downloading the same image while the previous image is still loading." Currently all browsers fail this test likely due to the memory cache (unspecified) or some non-spec-conforming form of the "list of available images". We should consider changing the spec to allow in-flight request coalescing, however until that is done we should at least have a test codifying the current state of the specification. [1]: https://html.spec.whatwg.org/multipage/images.html#list-of-available-images [2]: https://html.spec.whatwg.org/multipage/images.html#:~:text=completely%20available%20state.-,Add%20the%20image%20to%20the%20list%20of%20available%20images%20using%20the%20key,-key%2C%20with%20the R=domenic@chromium.org Bug: 994329 Change-Id: I9479ef286435704108e80e78096d5418ab014767 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3133524 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#917004} -- wpt-commits: d8a430f48a8ea112f0d5451d6feb02121001ef63 wpt-pr: 30259