9d28edca8e9f7d06b887a23e783260310941ac8d: Bug 1723277 - temporarily disable url/failure.html on Linux asan for failing with forbidden connection. CLOSED TREE default tip
Sebastian Hengst <archaeopteryx@coole-files.de> - Sat, 31 Jul 2021 13:30:16 +0200 - rev 587411
Push 147249 by archaeopteryx@coole-files.de at Sat, 31 Jul 2021 11:31:19 +0000
Bug 1723277 - temporarily disable url/failure.html on Linux asan for failing with forbidden connection. CLOSED TREE Subtest got added in bug 1720566. Test gets disabled to let whole wpt sync stick and shall be investigated next week.
a4ae3362c214d8f69f23d2ca545131d8b0f9a2d3: Bug 1723229 - switch css/selectors/first-letter-flag-001.html 'fail' expectations to 'pass' on Windows
Sebastian Hengst <archaeopteryx@coole-files.de> - Sat, 31 Jul 2021 13:21:44 +0200 - rev 587410
Push 147249 by archaeopteryx@coole-files.de at Sat, 31 Jul 2021 11:31:19 +0000
Bug 1723229 - switch css/selectors/first-letter-flag-001.html 'fail' expectations to 'pass' on Windows The test result got likely fixed by bug 1722763.
c5e75e74a44293aab75d80d065fa77e93dc4e015: Bug 1723229 - [wpt-sync] Update web-platform-tests to f29abfebc49d8278c352226cf0a0d46a29d0ea41, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 30 Jul 2021 22:16:37 +0000 - rev 587409
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1723229 - [wpt-sync] Update web-platform-tests to f29abfebc49d8278c352226cf0a0d46a29d0ea41, a=testonly MANUAL PUSH: wpt sync bot wpt-head: f29abfebc49d8278c352226cf0a0d46a29d0ea41 wpt-type: landing
080017f35da119431dd30bf0ee4c97815a6acfb0: Bug 1718877 [wpt PR 29552] - Test disturbed Response streams coming from different body sources., a=testonly
Andreu Botella <abb@randomunok.com> - Fri, 30 Jul 2021 22:14:34 +0000 - rev 587408
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1718877 [wpt PR 29552] - Test disturbed Response streams coming from different body sources., a=testonly Automatic update from web-platform-tests Test disturbed Response streams coming from different body sources. Deno's internal implementation of Request and Response bodies depends on their source – whether they were created from a stream or from a string or byte sequence. Deno passes the current tests that use Responses returned from the fetch API, but it would fail with Responses created from a string (denoland/deno#11211). -- wpt-commits: f29abfebc49d8278c352226cf0a0d46a29d0ea41 wpt-pr: 29552
8678f0c24d6649a008d3fa96d16e26c1205404fa: Bug 1718888 [wpt PR 29554] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 30 Jul 2021 17:48:49 +0000 - rev 587407
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1718888 [wpt PR 29554] - Update wpt metadata, a=testonly wpt-pr: 29554 wpt-type: metadata
278379ab96e6003e958cdb71ab5b9086096a6204: Bug 1718888 [wpt PR 29554] - Test the default Content-Type headers of Request and Response objects, a=testonly
Andreu Botella <abb@randomunok.com> - Fri, 30 Jul 2021 22:14:23 +0000 - rev 587406
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1718888 [wpt PR 29554] - Test the default Content-Type headers of Request and Response objects, a=testonly Automatic update from web-platform-tests Test the default Content-Type headers of Request and Response objects -- wpt-commits: 9dcc74815d059698cc6d86ef314c7693fac80d4e wpt-pr: 29554
d00170b56ef58e7eb8235c5105e575d92bc0b334: Bug 1722898 [wpt PR 29838] - Properly wire up scalabilityMode for setParameters., a=testonly
Mirta Dvornicic <mirtad@google.com> - Fri, 30 Jul 2021 22:14:18 +0000 - rev 587405
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722898 [wpt PR 29838] - Properly wire up scalabilityMode for setParameters., a=testonly Automatic update from web-platform-tests Properly wire up scalabilityMode for setParameters. Keep setting the number of temporal layers until WebRTC handles scalabilityMode for all codecs. Bug: 986069 Change-Id: I40e0deec2f9842de50ea0fcf672c93a44c3c556c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3060373 Reviewed-by: Harald Alvestrand <hta@chromium.org> Reviewed-by: Danil Chapovalov <danilchap@chromium.org> Commit-Queue: Mirta Dvornicic <mirtad@google.com> Cr-Commit-Position: refs/heads/master@{#907108} -- wpt-commits: 0a758bcce9d9daa8c005063a62d68b04da5daac1 wpt-pr: 29838
a774d4df0848c3b77172b1164bfd0ce989a6ee3a: Bug 1722463 [wpt PR 29799] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 30 Jul 2021 02:56:13 +0000 - rev 587404
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722463 [wpt PR 29799] - Update wpt metadata, a=testonly wpt-pr: 29799 wpt-type: metadata
e3f19d9e1ed42efd8224f25f22c7697ecb41917e: Bug 1722463 [wpt PR 29799] - Add non-fully active doc test for Geolocation, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Fri, 30 Jul 2021 22:14:09 +0000 - rev 587403
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722463 [wpt PR 29799] - Add non-fully active doc test for Geolocation, a=testonly Automatic update from web-platform-tests Add non-fully active doc test for Geolocation (#29799) -- wpt-commits: c85aa3307c29c969c3d153e1207e59738fa7764f wpt-pr: 29799
f1322aeef94cb185e76dcb21ac6effbb86d8e3ac: Bug 1722816 [wpt PR 29827] - [Scheduling APIs] Update TaskController constructor to match spec change, a=testonly
Scott Haseley <shaseley@chromium.org> - Fri, 30 Jul 2021 22:14:03 +0000 - rev 587402
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722816 [wpt PR 29827] - [Scheduling APIs] Update TaskController constructor to match spec change, a=testonly Automatic update from web-platform-tests [Scheduling APIs] Update TaskController constructor to match spec change This CL changes the TaskController constructor to take an optional dictionary instead of an optional priority to help future-proof the API. Spec: https://wicg.github.io/scheduling-apis/#sec-task-controller Issue: https://github.com/WICG/scheduling-apis/issues/26 Bug: 979017 Change-Id: I3b79f22505560b7f18549b6639b048c4b4cf0a79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3058867 Reviewed-by: Nate Chapin <japhet@chromium.org> Commit-Queue: Scott Haseley <shaseley@chromium.org> Cr-Commit-Position: refs/heads/master@{#906913} -- wpt-commits: 684c2c001aed0a1f9579f117febb659f1bbc0e64 wpt-pr: 29827
0fc69929c5ae9a6e064e2ba6603db1de61919461: Bug 1722831 [wpt PR 29832] - Cache Storage: Fix null deref with explicit undefined passed, a=testonly
Joshua Bell <jsbell@chromium.org> - Fri, 30 Jul 2021 22:13:55 +0000 - rev 587401
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722831 [wpt PR 29832] - Cache Storage: Fix null deref with explicit undefined passed, a=testonly Automatic update from web-platform-tests Cache Storage: Fix null deref with explicit undefined passed Given the IDL definition of two methods with args of the form (optional request, optional options), the bindings code expects two overloads in the implementation. The bindings code maps calls to the overloads differently if an explicit undefined is passed for request with no options vs. an explicit undefined is passed with an options arg, and the code wasn't expecting the request to be null. Bug: 1232955 Change-Id: I2ea29151dfaf4e764f221200ef4acb4784334a34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059555 Auto-Submit: Joshua Bell <jsbell@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#906793} -- wpt-commits: 1c62628e8bb4e8fda03a7e1af9aefbca60293381 wpt-pr: 29832
124caf9b10d7dc1c851ba0e1751cc2c82acb2f03: Bug 1722854 [wpt PR 29835] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 29 Jul 2021 18:51:24 +0000 - rev 587400
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722854 [wpt PR 29835] - Update wpt metadata, a=testonly wpt-pr: 29835 wpt-type: metadata
b6d30dfe376d5e177b25ce57eb35c825cfc188ed: Bug 1722854 [wpt PR 29835] - Fix two css-ui outline tests, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Fri, 30 Jul 2021 22:13:46 +0000 - rev 587399
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722854 [wpt PR 29835] - Fix two css-ui outline tests, a=testonly Automatic update from web-platform-tests Fix two css-ui outline tests - css/css-ui/outline-005: The test expected a rectangular outline outer edge, but both Chrome 94 and Firefox renders rounded outer edge. * Increase width of the outline and apply a rectangular clip to hide the difference of the outer edge. The test now checks whether the inner edge follows border-radius curve. * Add outline-offset:-1px to avoid visible anti-aliased pixels for both Chrome and Firefox. * Add fuzzy to allow slight color difference where the outline and the background intersect. - css/css-ui/outline-006: The reference expect green color (0,128,0) while the test produced (0,127,0) on all browsers regardless of whether outline-color:invert is supported. Now let the test produce the standard green color. Bug: 669473, 81556 Change-Id: Ic64a0d09eae99b7906287bc0c8bc086d00602d51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3058350 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#906752} -- wpt-commits: 699a9d5054abc867bd376710c83a28eeff387177 wpt-pr: 29835
de6dc0933e5b49c7ba1aa5a82c894773ffea3ec7: Bug 1722828 [wpt PR 29830] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 29 Jul 2021 17:35:18 +0000 - rev 587398
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722828 [wpt PR 29830] - Update wpt metadata, a=testonly wpt-pr: 29830 wpt-type: metadata
71e8aba445f1a0665bad93c057b2aa462621f8a1: Bug 1722828 [wpt PR 29830] - Remove 'tentative' from JSON module script filenames, a=testonly
Dan Clark <daniec@microsoft.com> - Fri, 30 Jul 2021 22:13:36 +0000 - rev 587397
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722828 [wpt PR 29830] - Remove 'tentative' from JSON module script filenames, a=testonly Automatic update from web-platform-tests Remove 'tentative' from JSON module script filenames Remove 'tenative' from JSON module script test filenames now that the HTML spec PR [1] is about to land. Also delete out-of-date README. [1] https://github.com/whatwg/html/pull/5658 Bug: 1132413 Change-Id: I306b5deddefc448d2b43f83942c490f2b217a565 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059740 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Dan Clark <daniec@microsoft.com> Cr-Commit-Position: refs/heads/master@{#906733} -- wpt-commits: 711b29c9ac887e0c72ea2bc16a29dd9b2fd78e24 wpt-pr: 29830
16840918ce3ad4ddb066337fadec5998b2df079e: Bug 1722830 [wpt PR 29831] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 29 Jul 2021 18:01:20 +0000 - rev 587396
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722830 [wpt PR 29831] - Update wpt metadata, a=testonly wpt-pr: 29831 wpt-type: metadata
588fb8b26ba08586aca4744e27d25e1f88df2e38: Bug 1722830 [wpt PR 29831] - Add BOM test for JSON and CSS module scripts, a=testonly
Dan Clark <daniec@microsoft.com> - Fri, 30 Jul 2021 22:13:25 +0000 - rev 587395
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722830 [wpt PR 29831] - Add BOM test for JSON and CSS module scripts, a=testonly Automatic update from web-platform-tests Add BOM test for JSON and CSS module scripts Add tests to validate that CSS and JSON module source is always decoded as UTF-8 even if a UTF-16 BOM is present. For JSON module scripts, this results in parse errors for UTF-16 sources. The CSS parser is more forgiving and doesn't throw an error, but instead fills in the invalid chars in the UTF-8 decoded source with U+FFFD REPLACEMENT CHARACTER. Bug: 992499,1132413 Change-Id: I91e2f79bf3cc44fd47d9b80e49b1285d452bb9ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059241 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Dan Clark <daniec@microsoft.com> Cr-Commit-Position: refs/heads/master@{#906734} -- wpt-commits: 656bbd1f820d6151d7b5f05284ee29f0119ffbcd wpt-pr: 29831
359fde8c7d8a7cd104dc5d15a900c85846cec72b: Bug 1722897 [wpt PR 29837] - [CSP] Fix WPT still using 'unsafe-hashed-attributes', a=testonly
Antonio Sartori <antoniosartori@chromium.org> - Fri, 30 Jul 2021 22:13:18 +0000 - rev 587394
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722897 [wpt PR 29837] - [CSP] Fix WPT still using 'unsafe-hashed-attributes', a=testonly Automatic update from web-platform-tests [CSP] Fix WPT still using 'unsafe-hashed-attributes' The test was failing because it was still using 'unsafe-hashed-attributes', which has been removed and replaced by 'unsafe-hashes'. Bug: 651742 Change-Id: Id1e05ed3b04216de3b28611d1150332cf7016c1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059490 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Auto-Submit: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#906692} -- wpt-commits: 4c8d190f9895fdd108f6b03b49345c850e352b43 wpt-pr: 29837
b8117966c1157bd8138ef1ea235e91f064da54b7: Bug 1722894 [wpt PR 29836] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 29 Jul 2021 13:22:40 +0000 - rev 587393
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722894 [wpt PR 29836] - Update wpt metadata, a=testonly wpt-pr: 29836 wpt-type: metadata
d318020d6e7348e09628a2a56c2ceb001e52f306: Bug 1722894 [wpt PR 29836] - [CSP] Fix WPT eval-blocked-in-about-blank-iframe, a=testonly
Antonio Sartori <antoniosartori@chromium.org> - Fri, 30 Jul 2021 22:13:09 +0000 - rev 587392
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722894 [wpt PR 29836] - [CSP] Fix WPT eval-blocked-in-about-blank-iframe, a=testonly Automatic update from web-platform-tests [CSP] Fix WPT eval-blocked-in-about-blank-iframe The test was failing for all vendors since it expected to get a securitypolicyviolation event in the parent frame instead of the frame where the eval was blocked. I rewrote the test in a modern way and deleted the old http blink test this one had been converted from. Bug: 651742 Change-Id: Ie8b7ae4842c0934b3c18086a2aee93c8a8ca292a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059564 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#906671} -- wpt-commits: d309992cc95cc8f340dd11065b51c4f1818a250c wpt-pr: 29836
cd00068d3ad86711aa960a66f906e15b88017bad: Bug 1722789 [wpt PR 29823] - Handle font values that contain "var()" for OffscreenCanvas, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Fri, 30 Jul 2021 22:13:03 +0000 - rev 587391
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722789 [wpt PR 29823] - Handle font values that contain "var()" for OffscreenCanvas, a=testonly Automatic update from web-platform-tests Handle font values that contain "var()" for OffscreenCanvas This is an offscreen equivalent to Bug 1131922. The fix for that bug introduced CSSParser::ParseFont, which handles var() and CSS-wide keywords correctly. Use CSSParser::ParseFont for OffscreenCanvasRenderingContext2D as well. Fixed: 1233430 Change-Id: Ic2119c64dec428f3b34f7fc0c15c86b6bcfe9195 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3058649 Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#906604} -- wpt-commits: e7d848ca78a17253dde9d49956bc00ae3ba91c57 wpt-pr: 29823
360dd21dbf7066d32b70028cb281b01960620a4a: Bug 1722788 [wpt PR 29822] - Rename Canvas2D.textLetterSpacing to Canvas2D.letterSpacing, a=testonly
Yi Xu <yiyix@chromium.org> - Fri, 30 Jul 2021 22:12:57 +0000 - rev 587390
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722788 [wpt PR 29822] - Rename Canvas2D.textLetterSpacing to Canvas2D.letterSpacing, a=testonly Automatic update from web-platform-tests Rename Canvas2D.textLetterSpacing to Canvas2D.letterSpacing Per discussion in https://github.com/w3ctag/design-reviews/issues/627, we have agreed to remove text prefix for attribute textLetterSpacing. So that thee attribute name letterSpacing follows the same naming conversion of other text attributes. Bug: 1233706 Change-Id: I8b37f046f5cdbfb28848ba3930e047203b061982 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3056509 Commit-Queue: Yi Xu <yiyix@chromium.org> Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#906594} -- wpt-commits: 34cb7e900e12fb6b9dc71b6c78d0aa9915dd18d4 wpt-pr: 29822
799f8d88457f37e2cf1e6ad77f5518a83b3c0c5b: Bug 1722270 [wpt PR 29781] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 29 Jul 2021 03:53:28 +0000 - rev 587389
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722270 [wpt PR 29781] - Update wpt metadata, a=testonly wpt-pr: 29781 wpt-type: metadata
6e4f4de64706468e67a800733b16c409153bc37f: Bug 1722270 [wpt PR 29781] - [css-text] Fix ID and PR rules., a=testonly
Makoto Kato <m_kato@ga2.so-net.ne.jp> - Fri, 30 Jul 2021 22:12:44 +0000 - rev 587388
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722270 [wpt PR 29781] - [css-text] Fix ID and PR rules., a=testonly Automatic update from web-platform-tests [css-text] Fix ID and PR rules. (#29781) css-text-line-break-de-pr-*.html tests seems to be break opportunity tests for PR and ID. But according to UAX #14, This rules are ID ÷ PR × ID. So these are incorrect. -- wpt-commits: 84330c9deccc99b84615ff142a13d27abae47a8e wpt-pr: 29781
56f89513673b2e09204c2da956527be2450db424: Bug 1722819 [wpt PR 29829] - Add reillyeon as reviewer for Geo API, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Fri, 30 Jul 2021 22:12:33 +0000 - rev 587387
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722819 [wpt PR 29829] - Add reillyeon as reviewer for Geo API, a=testonly Automatic update from web-platform-tests Add reillyeon as reviewer for Geo API (#29829) -- wpt-commits: 5dd2cefa9159da1f4c65697e9f96cf03185ad75d wpt-pr: 29829
2e9f637268123d1f53bd3c954e2422917d340019: Bug 1722787 [wpt PR 29821] - Rename Canvas2D.textWordSpacing to Canvas2D.wordSpacing, a=testonly
Yi Xu <yiyix@chromium.org> - Fri, 30 Jul 2021 22:12:28 +0000 - rev 587386
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722787 [wpt PR 29821] - Rename Canvas2D.textWordSpacing to Canvas2D.wordSpacing, a=testonly Automatic update from web-platform-tests Rename Canvas2D.textWordSpacing to Canvas2D.wordSpacing Per discussion in https://github.com/w3ctag/design-reviews/issues/627, we have agreed to remove text prefix for attribute textWordSpacing. So that thee attribute name wordSpacing follows the same naming conversion of other text attributes. Bug: 1233706 Change-Id: Ic735c7c4617572511fd37fe0928f8919e7fd3f69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3056391 Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: Aaron Krajeski <aaronhk@chromium.org> Commit-Queue: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/master@{#906470} -- wpt-commits: 7666067297aef38ba695aac42f703e627d9c6dd9 wpt-pr: 29821
4d22d32a93d4a4554cb65f78d20e0e4c11ddc7d0: Bug 1722751 [wpt PR 29819] - Fix fuzzy matching on dynamic-content-change-rendering.html, a=testonly
Philip Rogers <pdr@chromium.org> - Fri, 30 Jul 2021 22:12:18 +0000 - rev 587385
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722751 [wpt PR 29819] - Fix fuzzy matching on dynamic-content-change-rendering.html, a=testonly Automatic update from web-platform-tests Fix fuzzy matching on dynamic-content-change-rendering.html I added fuzzy matching to this test in https://crrev.com/905947 but that caused the test to fail everywhere [1] due to requiring a certain number of pixels to be different. This patch fixes that so the test now passes. I confirmed locally using the WPT runner that the test failed before https://crrev.com/905947 and now passes. I am unable to reproduce the original pixel differences seen on wpt.fyi so this is still a speculative fix. [1] https://wpt.fyi/results/html/semantics/forms/the-option-element/dynamic-content-change-rendering.html?label=master&label=experimental&aligned&q=dynamic-content-change-rendering.html Change-Id: I8ea0572fee2b84d518df2daff51742155f3b4846 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3059121 Auto-Submit: Philip Rogers <pdr@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#906448} -- wpt-commits: 36129dcea35999f0d05fd4969b531582c5a1a322 wpt-pr: 29819
cf85eab071f2e25ff80912fe3a1ccd26c4d08dff: Bug 1722636 [wpt PR 29814] - [webcodecs] Throw in allocationSize() if detached., a=testonly
Dan Sanders <sandersd@chromium.org> - Fri, 30 Jul 2021 22:12:13 +0000 - rev 587384
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722636 [wpt PR 29814] - [webcodecs] Throw in allocationSize() if detached., a=testonly Automatic update from web-platform-tests [webcodecs] Throw in allocationSize() if detached. https://github.com/w3c/webcodecs/issues/294 Change-Id: I6a9a7e74ac540b14f804bccdbed50f2a5effe4cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3057257 Commit-Queue: Dan Sanders <sandersd@chromium.org> Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#906354} -- wpt-commits: 2e0e4fe4b1aa66cb13709e6ed6475f02ce9b74b3 wpt-pr: 29814
6e8af1510c8ac156f28677e49df5588b9d7e6c83: Bug 1722532 [wpt PR 29807] - Don't pass transforms with negative M44 to MapEnclosedRectWith2dAxisAlignedTransform., a=testonly
L. David Baron <dbaron@chromium.org> - Fri, 30 Jul 2021 22:12:07 +0000 - rev 587383
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722532 [wpt PR 29807] - Don't pass transforms with negative M44 to MapEnclosedRectWith2dAxisAlignedTransform., a=testonly Automatic update from web-platform-tests Don't pass transforms with negative M44 to MapEnclosedRectWith2dAxisAlignedTransform. This introduces gfx::Transform::NonDegeneratePreserves2dAxisAlignment and uses it, rather than Preserves2dAxisAlignment, to guard all the calls to cc::MathUtil::MapEnclosedRectWith2dAxisAlignedTransform other than those in tests and those that result from gfx::OverlayTransformToTransform. Without this change, the new tests w-negative-002.html and w-negative-003.html hit the !hc0.ShouldBeClipped() DCHECK(), though w-negative-001.html does not, and this only happens with --disable-features=CompositeAfterPaint (which is still the default in web tests). Fixed: 455874, 1173218, 1229117 Change-Id: I671f04084a92ac6a71b83444fbba2ff9520dbc5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3055870 Reviewed-by: weiliangc <weiliangc@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Commit-Queue: David Baron <dbaron@chromium.org> Cr-Commit-Position: refs/heads/master@{#906332} -- wpt-commits: f0c21a69ac6374569e4c26e06b12a46c3a236396 wpt-pr: 29807
6a579f201170964d2bdcce73304cc60debfc0a90: Bug 1722365 [wpt PR 29787] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Jul 2021 20:55:43 +0000 - rev 587382
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722365 [wpt PR 29787] - Update wpt metadata, a=testonly wpt-pr: 29787 wpt-type: metadata
9e13d00e12e6df4f2ebfdae5d8a6e12b042324fb: Bug 1722365 [wpt PR 29787] - AppHistory: |canGo*| attributes should returns false if not fully active, a=testonly
Jinho Bang <zino@chromium.org> - Fri, 30 Jul 2021 22:11:58 +0000 - rev 587381
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722365 [wpt PR 29787] - AppHistory: |canGo*| attributes should returns false if not fully active, a=testonly Automatic update from web-platform-tests AppHistory: |canGo*| attributes should returns false if not fully active According to the spec[1], the document is not fully active, `canGoBack` and `canGoForward` attributes should return `false`. [1] https://wicg.github.io/app-history/#dom-apphistory-cangoback Bug: 1183545 Change-Id: I38faffdc6742e955fe810a3b304c77aa73afe915 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3054671 Reviewed-by: Domenic Denicola <domenic@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Commit-Queue: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/master@{#906330} -- wpt-commits: b8788faf1a5057a4ffdf73140c29b29ae9b06fb6 wpt-pr: 29787
9c12ed482b5c38e1ac04308d95b0d6d4fa35ab0b: Bug 1722706 [wpt PR 29818] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Jul 2021 16:40:09 +0000 - rev 587380
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722706 [wpt PR 29818] - Update wpt metadata, a=testonly wpt-pr: 29818 wpt-type: metadata
023ab32ceb8efc70c615cdc9332e43c2694b6ee3: Bug 1722706 [wpt PR 29818] - Attempt to de-flake simulcast WPTs., a=testonly
Henrik Boström <hbos@chromium.org> - Fri, 30 Jul 2021 22:11:48 +0000 - rev 587379
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722706 [wpt PR 29818] - Attempt to de-flake simulcast WPTs., a=testonly Automatic update from web-platform-tests Attempt to de-flake simulcast WPTs. I believe the reason for flakily timing out is that ramp-up does not happen quickly enough. Because I am unable to change the getUserMedia() resolution in external/wpt/webrtc/simulcast/simulcast.js (this causes timeout, either because the camera resolution is not supported by the fake capturer or because webrtc does not send QQVGA, not sure?) this CL changes the simulcast tests only to do 2 layers instead of 3. 2 layers instead of 3 should have a significantly lower ramp-up time in cases where ramp-up is not instant. The tests are already marked as having a long timeout so not sure how else to de-flake other than to reduce the bitrate. If any of the tests starts flaking again we should mark them all as flaky and file a common bug for all tests instead of having one crbug per test. Bug: chromium:1223773, chromium:1225643, chromium:1229785, chromium:1230534 Change-Id: I7a78ffc63a0521e4f971611d28c283c512371f43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3057576 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Philipp Hancke <philipp.hancke@googlemail.com> Cr-Commit-Position: refs/heads/master@{#906200} -- wpt-commits: 703b6682f0c5bb3e054ceca8568a75d37516d805 wpt-pr: 29818
e98e175d386f5b482817a4762d680018212db254: Bug 1722648 [wpt PR 29816] - Update tests reviewers for the Geolocation API, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Fri, 30 Jul 2021 22:11:42 +0000 - rev 587378
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722648 [wpt PR 29816] - Update tests reviewers for the Geolocation API, a=testonly Automatic update from web-platform-tests Update tests reviewers for the Geolocation API (#29816) -- wpt-commits: 8620992daa170d4dd9a0411efd67cc33ecd7bc72 wpt-pr: 29816
278e948fa873c778bf50a85617a93b769acdb46b: Bug 1722505 [wpt PR 29802] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Jul 2021 14:57:37 +0000 - rev 587377
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722505 [wpt PR 29802] - Update wpt metadata, a=testonly wpt-pr: 29802 wpt-type: metadata
e8e6dda7a4be853e3a46116de16d613220611812: Bug 1722505 [wpt PR 29802] - Rewrite popup-coop-by-sw-from-coop., a=testonly
Arthur Sonzogni <arthursonzogni@chromium.org> - Fri, 30 Jul 2021 22:11:31 +0000 - rev 587376
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722505 [wpt PR 29802] - Rewrite popup-coop-by-sw-from-coop., a=testonly Automatic update from web-platform-tests Rewrite popup-coop-by-sw-from-coop. Those tests are flaky, but nobody can reproduce. Rewrite those test entirely with more modern primitives, like the COEP:credentialless message passing API. Hoping this will fix the flakiness issue. Additional benefits: - The test is now defined in a single file instead of 5. - It is also 60 lines shorter. Fixed: 1151555 Bug: 1151555 Bug: https://github.com/web-platform-tests/wpt/pull/29746#issuecomment-885442292 Change-Id: I05e481760c6f1ba8cc6d6c5b9e5bc1af80a42c69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3035167 Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Antonio Sartori <antoniosartori@chromium.org> Cr-Commit-Position: refs/heads/master@{#906163} -- wpt-commits: 4dea1e26570741e12a25a6f05ec756d85dfcfd49 wpt-pr: 29802
0044519cd5f298021746da5ac454fc9f2f815e95: Bug 1722525 [wpt PR 29805] - [resource-timing] Clean up TAO reload test, a=testonly
Yoav Weiss <yoavweiss@chromium.org> - Fri, 30 Jul 2021 22:11:23 +0000 - rev 587375
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722525 [wpt PR 29805] - [resource-timing] Clean up TAO reload test, a=testonly Automatic update from web-platform-tests [resource-timing] Clean up TAO reload test Bug: 1171767 Change-Id: I3803497009f3c8417ead103666b77533f3ba7f20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3056038 Commit-Queue: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#906095} -- wpt-commits: 72581357e142f0be4968f47cbd21bc89b8c0c024 wpt-pr: 29805
76440dd5d5356f52c632cd4280d94d3b306f3632: Bug 1719632 [wpt PR 29606] - Use container elements to switch frames for testdriver rather than indices, a=testonly
James Graham <james@hoppipolla.co.uk> - Fri, 30 Jul 2021 22:11:15 +0000 - rev 587374
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1719632 [wpt PR 29606] - Use container elements to switch frames for testdriver rather than indices, a=testonly Automatic update from web-platform-tests Use container elements to select frames for testdriver switch_to_frame The previous setup used two execute_script calls and the length of window.frames to iterate over child crosing contexts. This failed if an iframe was removed in a way that races with the click. Element identifiers should be more stable since they are unaffected by other DOM manipulation. -- Change webdriver imports in executorwebdriver I'm actually unsure if this was working correctly before; the use of client.WebDriverException and subclasses doesn't look like it ought to work given client.py doesn't import those. -- wpt-commits: d846ad02866ed966cf3e2123d6bacb2f7bdc73b7, e6bc8ae0357ddaabf554c3c04ef1630bb2370a05 wpt-pr: 29606
cc0054ff51e27581482be0f57b506f8d6d420844: Bug 1722495 [wpt PR 29801] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Jul 2021 13:27:17 +0000 - rev 587373
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722495 [wpt PR 29801] - Update wpt metadata, a=testonly wpt-pr: 29801 wpt-type: metadata
87467ba0385c09f8a3edae8608527e6f56ce2558: Bug 1722495 [wpt PR 29801] - Add WPT for anonymous iframes service workers partitioning, a=testonly
Antonio Sartori <antoniosartori@chromium.org> - Fri, 30 Jul 2021 22:11:06 +0000 - rev 587372
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722495 [wpt PR 29801] - Add WPT for anonymous iframes service workers partitioning, a=testonly Automatic update from web-platform-tests Add WPT for anonymous iframes service workers partitioning This CL adds a Web Platform Test checking that anonymous iframes have partitioned service workers w.r.t. normal iframes. The test is currently failing, but will go through once we plumb the storage key's nonce into service workers. Bug: 1226469,1199077 Change-Id: Iebee833c4a7ac0aa7125b6f772b80be573be6405 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3055353 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#906080} -- wpt-commits: f2813342c5383b1868f778fd7ba4259d57024d89 wpt-pr: 29801
9ef325130d7d607a9f0521629112b9295408067e: Bug 1722377 [wpt PR 29791] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Jul 2021 13:19:41 +0000 - rev 587371
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722377 [wpt PR 29791] - Update wpt metadata, a=testonly wpt-pr: 29791 wpt-type: metadata
80a64005448b1a9b98263cbae6fda9f2d25d32c8: Bug 1722377 [wpt PR 29791] - URLPattern: Implement compareComponent() method., a=testonly
Ben Kelly <wanderview@chromium.org> - Fri, 30 Jul 2021 22:10:55 +0000 - rev 587370
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722377 [wpt PR 29791] - URLPattern: Implement compareComponent() method., a=testonly Automatic update from web-platform-tests URLPattern: Implement compareComponent() method. This CL adds a prototype URLPattern.compareComponent() to provide a natural ordering to URLPattern pattern strings. This was based on feedback from routing framework authors and there is some discussion in: https://github.com/WICG/urlpattern/issues/61 The general algorithm is to compare the component patterns Part by Part. The PartType, Modifier, and text contents are compared for each Part, but group names are not considered. The end result is a mostly lexicographical ordering based on fixed text. Matching groups and modifiers are ordered such that more restrictive patterns are greater. Bug: 1232795 Change-Id: I8474cd7d7689e657c9c74c552ad630cdcdd86c95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3052630 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#906025} -- wpt-commits: 2f4642d50f5c868a281cf3f20c8c7122e1f6b89a wpt-pr: 29791
21d51020f1bd20fa6b646415d866dce1e24bd5c8: Bug 1722611 [wpt PR 29810] - Add fuzzy matching to dynamic-content-change-rendering.html, a=testonly
Philip Rogers <pdr@chromium.org> - Fri, 30 Jul 2021 22:10:49 +0000 - rev 587369
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722611 [wpt PR 29810] - Add fuzzy matching to dynamic-content-change-rendering.html, a=testonly Automatic update from web-platform-tests Add fuzzy matching to dynamic-content-change-rendering.html This test passes locally but is failing on WPT due to minor pixel differences, likely due to how the select element is resized: https://wpt.fyi/results/html/semantics/forms/the-option-element/dynamic-content-change-rendering.html?label=master&label=experimental&aligned&q=dynamic-content-change-rendering.html Change-Id: I94592ad3512a09ae93181c7a92e8fed7861904d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3057512 Auto-Submit: Philip Rogers <pdr@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#905947} -- wpt-commits: f93baa8f6c6aa82287a3f49491f34114d6a301a5 wpt-pr: 29810
e305ec092bad9cde5aa76f796ff7aa2b1c033b8d: Bug 1722444 [wpt PR 29798] - Fix Canvas 2d attribute spelling, a=testonly
Yi Xu <yiyix@chromium.org> - Fri, 30 Jul 2021 22:10:44 +0000 - rev 587368
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722444 [wpt PR 29798] - Fix Canvas 2d attribute spelling, a=testonly Automatic update from web-platform-tests Fix Canvas 2d attribute spelling TextRendering properties are saved as "Auto", "GeometricPrecision", "OptimizeSpeed", etc, which is wrong and it is supposed to start with lower case letters instead, i.e., "auto", "geometricPrecision", "optimizeSpeed", etc. This similar mistake were made for FontKerning, FontVariant and FontStretch. This Cl fixes the spelling issues for these Canvas 2D attributes. Bug: 1230242 Change-Id: I8e5e4cd60fcf75ec5de984a880c5b5b9426a75e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3055118 Reviewed-by: Justin Novosad <junov@chromium.org> Commit-Queue: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/master@{#905809} -- wpt-commits: e2a08cb33180c282ad5c3b36e9d92d21bcd37346 wpt-pr: 29798
ce7a2635363ad20500851d44abe12d20be0508c8: Bug 1462661 [wpt PR 11069] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 30 Jul 2021 09:44:36 +0000 - rev 587367
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1462661 [wpt PR 11069] - Update wpt metadata, a=testonly wpt-pr: 11069 wpt-type: metadata
5b02cbe342922840972ac0896118defe9962884b: Bug 1462661 [wpt PR 11069] - Add tests for structuredClone, a=testonly
Surma <surma@surma.dev> - Fri, 30 Jul 2021 22:10:28 +0000 - rev 587366
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1462661 [wpt PR 11069] - Add tests for structuredClone, a=testonly Automatic update from web-platform-tests Add tests for structuredClone Follows https://github.com/whatwg/html/pull/3414. -- wpt-commits: 7cfc0be8d4d4c3ae374e1f8444a2309c0eefc563 wpt-pr: 11069
220f3450033634d8a66efbdeb248fd3df3d55339: Bug 1722421 [wpt PR 29796] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Jul 2021 10:39:57 +0000 - rev 587365
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722421 [wpt PR 29796] - Update wpt metadata, a=testonly wpt-pr: 29796 wpt-type: metadata
91f25b90c5f512d0d8217242055e84b3e440da8a: Bug 1722421 [wpt PR 29796] - Fix and re-enable SameSite cookie reload WPTs, a=testonly
Lily Chen <chlily@chromium.org> - Fri, 30 Jul 2021 22:10:18 +0000 - rev 587364
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722421 [wpt PR 29796] - Fix and re-enable SameSite cookie reload WPTs, a=testonly Automatic update from web-platform-tests Fix and re-enable SameSite cookie reload WPTs The SameSite cookie WPTs dealing with reloaded pages have been disabled for a long time for failures. A recent spec change clarified the correct behavior for SameSite cookies on reload navigations: https://github.com/httpwg/http-extensions/pull/1384 The reloads used in these tests are renderer-initiated, as opposed to browser-initiated (triggered by user interface elements), so they should be considered same-site requests. The SameSite context of the initial navigation need not be the same as the context of the reloaded navigation. The tests are modified to support two different statuses. One of the tests, involving POST requests, is still failing, but for a different reason, and has been moved to the appropriate section of TestExpectations. Bug: 843945 Change-Id: Ifa5c4431e3761534246c150ead2e1823a712bfd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3053934 Reviewed-by: Steven Bingler <bingler@chromium.org> Commit-Queue: Lily Chen <chlily@chromium.org> Cr-Commit-Position: refs/heads/master@{#905760} -- wpt-commits: 48b6d27f1fc41d82b71a22daa4cf1a0698bddc02 wpt-pr: 29796
fba4562da99945ba371046ebb79dc45c406ba9e4: Bug 1721988 [wpt PR 29761] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 27 Jul 2021 08:59:36 +0000 - rev 587363
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721988 [wpt PR 29761] - Update wpt metadata, a=testonly wpt-pr: 29761 wpt-type: metadata
9b5bf5fa20b258869e34eaa94b98de7bfaedc082: Bug 1721988 [wpt PR 29761] - Add/Update Core-AAM tests (for ARIA+Core-AAM CR exit-criteria testing), a=testonly
joanmarie <jdiggs@igalia.com> - Fri, 30 Jul 2021 22:10:00 +0000 - rev 587362
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721988 [wpt PR 29761] - Add/Update Core-AAM tests (for ARIA+Core-AAM CR exit-criteria testing), a=testonly Automatic update from web-platform-tests Add/Update Core-AAM tests (for ARIA+Core-AAM CR exit-criteria testing) (#29761) -- wpt-commits: 697cefa77cd5180e3c03944c8c8fd28df56dbd9a wpt-pr: 29761
f45f59c0197644f7e9006db55a25ca00ce6f82df: Bug 1722024 [wpt PR 29764] - Reland: '[fsa] Implement truncate for the sync access handle', a=testonly
Andreas Haas <ahaas@chromium.org> - Fri, 30 Jul 2021 22:09:19 +0000 - rev 587361
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722024 [wpt PR 29764] - Reland: '[fsa] Implement truncate for the sync access handle', a=testonly Automatic update from web-platform-tests Reland: '[fsa] Implement truncate for the sync access handle' In the original CL a test with the 'truncate' operation was also added to the close-tests, but a test expectation was not added for this test. Original message: The implementation is ported from the implementation of Storage Foundation in https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/native_io/native_io_file_async.cc. This is part of the efforts to merge Storage Foundation into OPFS. Note that this CL does not contain the implementation for MacOS below version 10.15. The old MacOS needs special handling, which will be added in a separate CL. Bug: chromium:1218431 Change-Id: I78f6cadc38a6b46c3b6bc7832491f08c59317db9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3048192 Reviewed-by: Marijn Kruisselbrink <mek@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#905623} -- wpt-commits: 30e54c16c4a40c9db27435657eaf1d824cb7c416 wpt-pr: 29764
6509d72f73daaf5c3e314debc48d3667b780980c: Bug 1721660 [wpt PR 29738] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 27 Jul 2021 06:41:50 +0000 - rev 587360
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721660 [wpt PR 29738] - Update wpt metadata, a=testonly wpt-pr: 29738 wpt-type: metadata
f77ac676e613c0c068a6bfb6f125c7ce80e2caf2: Bug 1721660 [wpt PR 29738] - HTML: self.reportError(), a=testonly
Anne van Kesteren <annevk@annevk.nl> - Fri, 30 Jul 2021 22:09:05 +0000 - rev 587359
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721660 [wpt PR 29738] - HTML: self.reportError(), a=testonly Automatic update from web-platform-tests HTML: self.reportError() For https://github.com/whatwg/html/pull/1196. -- wpt-commits: c3cb1109a30e82ceccdf4202d26f6c6648bbef70 wpt-pr: 29738
3470a54cb6cff31096c334f1c05313911de630de: Bug 1721509 [wpt PR 29724] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 27 Jul 2021 00:50:57 +0000 - rev 587358
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721509 [wpt PR 29724] - Update wpt metadata, a=testonly wpt-pr: 29724 wpt-type: metadata
ea180423f5bd9fc400ea49855d53b52226fcbc7f: Bug 1721509 [wpt PR 29724] - [LayoutNG] OOF inline offset with inline containing block, a=testonly
Alison Maher <almaher@microsoft.com> - Fri, 30 Jul 2021 22:08:57 +0000 - rev 587357
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721509 [wpt PR 29724] - [LayoutNG] OOF inline offset with inline containing block, a=testonly Automatic update from web-platform-tests [LayoutNG] OOF inline offset with inline containing block When computing the inline containing block geometry in ComputeInlineContainerGeometryForFragmentainer(), we had originally calculated the offsets so that they were relative to the top of the fragmentation context root. However, we weren't taking the inline offset of the containing block into account, which can lead to the wrong OOF offset. Instead, calculate the offsets so that they are relative to the containing block and add the offset of the containing block relative to the fragmentation context root during the final inline CB rect offset calculation. This ensures that we are also adding in the inline offset from the containing block. This update also resulted in a simplification of the number of input variables and calculations previously needed in ComputeInlineContainerGeometryForFragmentainer(). Bug: 1231218 Change-Id: I6d5bd2bffab0fde0a7b29b405494b33273eba2f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3042100 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#905485} -- wpt-commits: da6bac9cd3c368dc48e131c6c58823358d9e2f45 wpt-pr: 29724
20e96eee4a207f4510a215ec558a0d522fdb9c1f: Bug 1719644 [wpt PR 29610] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 27 Jul 2021 00:02:37 +0000 - rev 587356
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1719644 [wpt PR 29610] - Update wpt metadata, a=testonly wpt-pr: 29610 wpt-type: metadata
84dc9e878b3cb393f05418a46f1e14446b96b316: Bug 1719644 [wpt PR 29610] - Implement minsize/maxsize attributes, a=testonly
Frédéric Wang <fwang@igalia.com> - Fri, 30 Jul 2021 22:08:47 +0000 - rev 587355
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1719644 [wpt PR 29610] - Implement minsize/maxsize attributes, a=testonly Automatic update from web-platform-tests Implement minsize/maxsize attributes This is the third patch of a series of CL to implement MathML stretchy operators. It implements step 5 from [1] so that users can specify some minsize/maxsize values for vertical operators. It also adds missing invalidation of minsize/maxsize when parsing them on the DOM side. This CL also fixes the test mo-minsize-maxsize-001.html when checking minsize with target size is 0. The test seemed to assume the minsize would be double when applying the symmetric property but this is not what is currently described in the spec. [1] https://w3c.github.io/mathml-core/#layout-of-operators Bug: 6606, 1124301 Change-Id: I4358ea65b0d74667ee6c5d8b2a11c6403f86e210 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3013895 Commit-Queue: Frédéric Wang <fwang@igalia.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#905460} -- wpt-commits: d7e150b87b8eee8d4117950e0aec931974069a53 wpt-pr: 29610
b0b43d2a31c14d085a86ecfb6423a349a85ee990: Bug 1722381 [wpt PR 29792] - Re-enable SameSite cookie iframe WPTs, a=testonly
Lily Chen <chlily@chromium.org> - Fri, 30 Jul 2021 22:08:41 +0000 - rev 587354
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722381 [wpt PR 29792] - Re-enable SameSite cookie iframe WPTs, a=testonly Automatic update from web-platform-tests Re-enable SameSite cookie iframe WPTs These tests were temporarily disabled due to an incompatibility between Firefox and Chromium. Now that this has been resolved by a spec PR (https://github.com/httpwg/http-extensions/pull/1428), the tests can be re-enabled. Additionally, one of the tests was adjusted to reflect the behavior for redirects specified in https://github.com/httpwg/http-extensions/pull/1348, which is enabled as part of --enable-experimental-web-platform-features. Bug: 1074441 Change-Id: I7e1deadf0c080927cc328b54d300d5d418fa5c6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3054294 Reviewed-by: Steven Bingler <bingler@chromium.org> Commit-Queue: Lily Chen <chlily@chromium.org> Cr-Commit-Position: refs/heads/master@{#905421} -- wpt-commits: d4deee9e5303f3c09f65bc0d40783cc18a30606e wpt-pr: 29792
dd6f70f54e15d6f35d84f2613050f8d7d23fa285: Bug 1721957 [wpt PR 29758] - Remove legacy-samesite Web Platform Tests, a=testonly
Lily Chen <chlily@chromium.org> - Fri, 30 Jul 2021 22:08:34 +0000 - rev 587353
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1721957 [wpt PR 29758] - Remove legacy-samesite Web Platform Tests, a=testonly Automatic update from web-platform-tests Remove legacy-samesite Web Platform Tests SameSite-Lax-by-default and SameSite=None-requires-Secure have been standardized ([1], [2]) and launched in Chromium [3] as well as Firefox [4]. The WPTs testing "legacy" behavior are no longer needed, and they are also failing on wpt.fyi [5]. This change removes the legacy-samesite virtual test suite, as well as the ?legacy-samesite variant of the tests in wpt/cookie/samesite/. The test for SameSite=None-requires-Secure also loses its "tentative" designation. Chromium will soon no longer support the configuration used in the virtual test suite, so there would be no way to run these tests anyway. [1] https://github.com/httpwg/http-extensions/pull/1325 [2] https://github.com/httpwg/http-extensions/pull/1323 [3] https://crrev.com/c/2231445 [4] https://hacks.mozilla.org/2020/08/changes-to-samesite-cookie-behavior/ [5] https://wpt.fyi/results/cookies/samesite?run_id=5099687737556992&run_id=5641857632567296&run_id=5678463840157696&run_id=5638004375814144 Bug: 961439, 1211388 Change-Id: Idb3c835908bcd61dde3593b4fb4f9349e738031f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3047679 Reviewed-by: Steven Bingler <bingler@chromium.org> Commit-Queue: Lily Chen <chlily@chromium.org> Cr-Commit-Position: refs/heads/master@{#905289} -- wpt-commits: 939731a4f020de9afac2c4bf8c4de67eb9992e68 wpt-pr: 29758
d9f1d70f1168f1b104313d8b93ea0912a52485f7: Bug 1722321 [wpt PR 29785] - [ResourceTiming]: Update WPTs concerning opaque origins, a=testonly
Tom McKee <tommckee@chromium.org> - Fri, 30 Jul 2021 22:08:25 +0000 - rev 587352
Push 147248 by wptsync@mozilla.com at Sat, 31 Jul 2021 09:27:10 +0000
Bug 1722321 [wpt PR 29785] - [ResourceTiming]: Update WPTs concerning opaque origins, a=testonly Automatic update from web-platform-tests [ResourceTiming]: Update WPTs concerning opaque origins Both TAO-null-opaque-origin.html and TAO-case-insensitive-null-opaque-origin.sub.html test the Resource Timing API when resources are fetched from an opaque origin context. This change updates those tests to conform to wpt/resource-timing/CodingConventions.md. Bug: 1171767 Change-Id: I3bfbaa4a714a4582a5c900aa345df118828e1e0e GithubIssue: https://github.com/w3c/resource-timing/issues/254 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3042198 Commit-Queue: Tom McKee <tommckee@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#905292} -- wpt-commits: 39fb1e25c09fd193d6a5675c0ebee0d8d00feb09 wpt-pr: 29785
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -60 tip