b7de827ad53013741cee8a2ba6ca1dc47159c028: Bug 1704910 [wpt PR 28460] - chore: restructure xhr/formdata tests, a=testonly
Luca Casonato <lucacasonato@yahoo.com> - Fri, 23 Apr 2021 10:17:51 +0000 - rev 577251
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1704910 [wpt PR 28460] - chore: restructure xhr/formdata tests, a=testonly Automatic update from web-platform-tests XHR: restructure FormData tests This commit restrucutres xhr/formdata tests that do not require a form element to be .any.js tests, and thus runnable outside the browser, and in workers (like in Deno). This commit only moves tests around (no changes or removals), with the exception of the "Passing a String object to FormData.set should work" and "Passing a String object to FormData.append should work." tests because the tests are exact replicas of the "formdata with string" test in xhr/formdata.html. Because of that they have been removed. -- wpt-commits: e45a9f9e65d039c76817ee2a6a1ef02c9311a1cb wpt-pr: 28460
da4db35e7325d059eff40083b1c95d62d4f001e7: Bug 1705264 [wpt PR 28499] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 15 Apr 2021 06:45:04 +0000 - rev 577250
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705264 [wpt PR 28499] - Update wpt metadata, a=testonly wpt-pr: 28499 wpt-type: metadata
b69b49691a48cddbf0c7436d26f29810977e89f0: Bug 1705264 [wpt PR 28499] - implement crypto.randomUUID(), a=testonly
Benjamin Coe <bencoe@google.com> - Fri, 23 Apr 2021 10:17:38 +0000 - rev 577249
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705264 [wpt PR 28499] - implement crypto.randomUUID(), a=testonly Automatic update from web-platform-tests implement crypto.randomUUID() Implementation of crypto.randomUUID() using base/guid which indicates "A cryptographically secure random source will be used". Refs: https://wicg.github.io/uuid/ Bug: 1197594 Change-Id: I0f5402b4d83a5d89f02425d8050a7737264672dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2804758 Commit-Queue: Benjamin Coe <bencoe@google.com> Reviewed-by: Domenic Denicola <domenic@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#872711} -- wpt-commits: 15874bf6200f929ecb91726aab4c8e4d1412fee0 wpt-pr: 28499
6bb5bc0af0694d01d625500eebd754cc91a69463: Bug 1700509 [wpt PR 28201] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 15 Apr 2021 04:15:39 +0000 - rev 577248
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1700509 [wpt PR 28201] - Update wpt metadata, a=testonly wpt-pr: 28201 wpt-type: metadata
b03075225de2d2b53974bba8db7b0d5c326b3242: Bug 1700509 [wpt PR 28201] - Update offsetParent behavior in shadow trees, a=testonly
Joey Arhar <jarhar@chromium.org> - Fri, 23 Apr 2021 10:17:30 +0000 - rev 577247
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1700509 [wpt PR 28201] - Update offsetParent behavior in shadow trees, a=testonly Automatic update from web-platform-tests Update offsetParent behavior in shadow trees New behavior for offsetParent in shadow trees was discussed in [1] and [2]. This lead to a chromium patch [3] which changed the behavior. After [3] landed, the desired behavior in the discussions in [1] and [2] seemed to have changed. Unfortunately, the author of [3] was no longer working on chromium. This new behavior was then added to the spec and landed in webkit [4] and firefox [5], and a WPT was added for it [6]. This patch implements the new behavior to follow suit with webkit and firefox based on the WPT in [6]. Unfortunately, there are several tests which are either internal to chromium or are only passing in chromium which appear to oppose this new behavior and will have to be updated or removed: - external/wpt/css/css-contain/content-visibility/content-visibility-035.html - external/wpt/css/css-contain/content-visibility/content-visibility-044.html - fast/dom/shadow/offset-parent-does-not-leak-ua-shadow.html - shadow-dom/offsetParent.html For shadow-dom/offsetParent.html, I verified that firefox and safari both currently fail the same tests which this patch does. [1] https://github.com/WICG/webcomponents/issues/497 [2] https://github.com/w3c/csswg-drafts/issues/159 [3] https://chromium.googlesource.com/chromium/src/+/18d455ee833f6a30dcbe2755380861eb75cd9f6f [4] https://trac.webkit.org/changeset/239313/webkit [5] https://bugzilla.mozilla.org/show_bug.cgi?id=1514074 [6] https://wpt.fyi/results/shadow-dom/offsetParent-across-shadow-boundaries.html Fixed: 920069 Change-Id: I168edc5ad0e4fcb92d0c4a440623f2424b14a988 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2775208 Reviewed-by: Mason Freed <masonf@chromium.org> Reviewed-by: vmpstr <vmpstr@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/master@{#872658} -- wpt-commits: 8d8b8c4e2e42d07398fd5e98b541ee239e1d35a4 wpt-pr: 28201
c981b467789021519b396d3c4ce2347d68996a49: Bug 1705222 [wpt PR 28484] - Background Fetch: use permission context directly when initiating fetch., a=testonly
Evan Stade <estade@chromium.org> - Fri, 23 Apr 2021 10:17:25 +0000 - rev 577246
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705222 [wpt PR 28484] - Background Fetch: use permission context directly when initiating fetch., a=testonly Automatic update from web-platform-tests Background Fetch: use permission context directly when initiating fetch. This reduces duplicated logic between BackgroundFetchDelegateImpl and BackgroundFetchPermissionContext. It also forces the logic to align. Specifically, the permission context returned ALLOW when automatic DLs were allowed, but the implementation enforced ASK even if auto DLs are allowed. This temporarily regresses WebLayer because there's no Background Fetch permission context there, but that will be addressed soon. Bug: 1189247, 1057770 Change-Id: I5441f00835c186826927d2ef38612c8e55eb049f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2800512 Commit-Queue: Evan Stade <estade@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Reviewed-by: Mugdha Lakhani <nator@chromium.org> Cr-Commit-Position: refs/heads/master@{#872641} -- wpt-commits: c7646854131fe696fa38ae8b5e3e611dc6f52d19 wpt-pr: 28484
92c8b13b01ac816877d7ec6c0a762a3bb7b3edc1: Bug 1705224 [wpt PR 28486] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 15 Apr 2021 03:27:13 +0000 - rev 577245
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705224 [wpt PR 28486] - Update wpt metadata, a=testonly wpt-pr: 28486 wpt-type: metadata
e62a3350c7c285daf76beadc5b39bc4ca8efbcb6: Bug 1705224 [wpt PR 28486] - webcodecs: Implementation of VideoEncoder.isConfigSupported(), a=testonly
Eugene Zemtsov <eugene@chromium.org> - Fri, 23 Apr 2021 10:17:10 +0000 - rev 577244
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705224 [wpt PR 28486] - webcodecs: Implementation of VideoEncoder.isConfigSupported(), a=testonly Automatic update from web-platform-tests webcodecs: Implementation of VideoEncoder.isConfigSupported() Bug: 1176442 Change-Id: I2463090994eb946284eeee1e62ed53ebd7c9584c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2823770 Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Reviewed-by: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#872626} -- wpt-commits: f4351ba70263b622c24c6b79ff57ecef2916f0b6 wpt-pr: 28486
83e3c4858f70d7547a07d4738401d70a496156cc: Bug 1705204 [wpt PR 28483] - [ReplacedNG] Compute min-content/max-content within ComputeReplacedSize., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Fri, 23 Apr 2021 10:17:06 +0000 - rev 577243
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705204 [wpt PR 28483] - [ReplacedNG] Compute min-content/max-content within ComputeReplacedSize., a=testonly Automatic update from web-platform-tests [ReplacedNG] Compute min-content/max-content within ComputeReplacedSize. \o/ This computes the min/max content sizes for replaced elements directly within ComputeReplacedSize. This allows us to simply call: ComputeReplacedSize(node, space) and get the correct size for replaced elements with only those arguments! Bug: 1114280 Change-Id: Ieedacf5f0ee814668f1c2c4633946b0bbb27e89f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2818210 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#872558} -- wpt-commits: 1c760edb722b39d5b69dece6b4ec463bf3dee9cb wpt-pr: 28483
64f912b7c65ee1551a639fbd706b9e95a80867e1: Bug 1705189 [wpt PR 28482] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 14 Apr 2021 23:05:51 +0000 - rev 577242
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705189 [wpt PR 28482] - Update wpt metadata, a=testonly wpt-pr: 28482 wpt-type: metadata
29b3c96abe795202a19abb3f4f52ce48c6885902: Bug 1705189 [wpt PR 28482] - [TablesNG] Tentative baseline tests, a=testonly
Aleks Totic <atotic@chromium.org> - Fri, 23 Apr 2021 10:16:59 +0000 - rev 577241
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705189 [wpt PR 28482] - [TablesNG] Tentative baseline tests, a=testonly Automatic update from web-platform-tests [TablesNG] Tentative baseline tests More upstreaming of master table patch tests. Change-Id: I4bc78ea05a5041f7adf7eb57de5b2f4c9a210098 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2823578 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#872548} -- wpt-commits: 7011e122cd3f56a6269668eb0fd3f4c5a2488788 wpt-pr: 28482
93ec388cd51d027b9189d1fbb830f01be59cbf53: Bug 1693598 [wpt PR 27681] - Add pointerevents' properties to gpubenchmarking.PointerActionSequence, a=testonly
Lan Wei <lanwei@chromium.org> - Fri, 23 Apr 2021 10:16:54 +0000 - rev 577240
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1693598 [wpt PR 27681] - Add pointerevents' properties to gpubenchmarking.PointerActionSequence, a=testonly Automatic update from web-platform-tests Add pointerevents' properties to gpubenchmarking.PointerActionSequence I have added the pointerevents' properties to WebDriver Action API, and some WPT tests. Because gpubenchmarking.PointerActionSequence does not have these properties, these tests are failing on content shell. This CL will add the properties to gpubenchmarking.PointerActionSequence as well. Bug: 1147126 Change-Id: I55d14a342d63461cdfab6a31389a7c0bb9757bbb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2683954 Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Reviewed-by: Philip J├Ągenstedt <foolip@chromium.org> Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#872509} -- wpt-commits: 51639933704c8a87a2ac7d728e84613cbef3c9e0 wpt-pr: 27681
1dc0e4b98f82406f2f58efa0999dde969e967c1c: Bug 1701666 [wpt PR 28280] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 14 Apr 2021 21:17:13 +0000 - rev 577239
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1701666 [wpt PR 28280] - Update wpt metadata, a=testonly wpt-pr: 28280 wpt-type: metadata
0e4161f18fc08140fc7045ba49e49631786f890d: Bug 1701666 [wpt PR 28280] - Initial implementation of scrollbar-width, a=testonly
Felipe Erias <felipeerias@igalia.com> - Fri, 23 Apr 2021 10:16:46 +0000 - rev 577238
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1701666 [wpt PR 28280] - Initial implementation of scrollbar-width, a=testonly Automatic update from web-platform-tests Initial implementation of scrollbar-width ComputedStyle::HasCustomScrollbarStyle() returns true if a custom style for the scrollbar has been set via ::-webkit-scrollbar and the value of scrollbar-width has not been changed from the default. This replaces HasPseudoElementStyle(kPseudoIdScrollbar) so the standard properties for styling scrollbars take precedence over the non-standard method. For convenience, the method Scrollbar::CSSScrollbarWidth() returns the value of the scrollbar-width property in that scrollbar's style. Scrollbar themes take scrollbar-width into account when calculating a scrollbar's thickness, margin, etc. When scrollbar-width is "none", scrollbar themes simply return a thickness of 0 to hide the scrollbar. WebThemeEngine::ScrollbarStyle includes the thickness and margin values for the thin variant. ScrollbarThemeMac uses NSRegularControlSize and NSSmallControlSize to size and display the appropriate type of scrollbar for the default and thin variants. ScrollbarThemeOverlay stores the thickness and margin for the thin variant, although at the moment these values are the same as the default (pending changes to WebThemeEngine). The same applies to the ScrollbarThemeOverlayMobile subclass. ScrollbarThemeAura simply scales the default scrollbar by a 2/3 ratio to paint the thin variant. In the future, the theme should include specific width values for this variant. Perhaps it would also be desirable to use a different set of graphic elements. WPT tests are included. Bug: 891944 Change-Id: I2d451f07de5a16e6cada8a68ae01da7358e8652a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2681340 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Felipe Erias <felipeerias@igalia.com> Cr-Commit-Position: refs/heads/master@{#872500} -- wpt-commits: f68f2e6bbe1c50a30e690243b64906f2a490e515 wpt-pr: 28280
904d3437c0a072a375093c8197b82203b1c3d18c: Bug 1705149 [wpt PR 28481] - Add a test for crbug.com/1167352, a=testonly
Xianzhu Wang <wangxianzhu@chromium.org> - Fri, 23 Apr 2021 10:16:38 +0000 - rev 577237
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705149 [wpt PR 28481] - Add a test for crbug.com/1167352, a=testonly Automatic update from web-platform-tests Add a test for crbug.com/1167352 Bug: 1167352 Change-Id: Id340d704e80c03cfc49a00a7f840c6866c450034 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2822813 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#872482} -- wpt-commits: b3804b4ee1c96551ef3eccb7d4fb578db0ff3d21 wpt-pr: 28481
40a7337356d75a0e31e19c864cb9ec7154eeeefb: Bug 1705135 [wpt PR 28479] - [css-color-4] Remove another test for color() fallback, a=testonly
Sam Weinig <weinig@apple.com> - Fri, 23 Apr 2021 10:16:33 +0000 - rev 577236
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705135 [wpt PR 28479] - [css-color-4] Remove another test for color() fallback, a=testonly Automatic update from web-platform-tests [css-color-4] Remove another test for color() fallback (#28479) color() function fallback is no longer part of the spec. -- wpt-commits: b6e84edf4a398cc48f4983cbd8398858816996ae wpt-pr: 28479
75d77c8131208938db250a58febc99da467239af: Bug 1705128 [wpt PR 28476] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 14 Apr 2021 17:31:16 +0000 - rev 577235
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705128 [wpt PR 28476] - Update wpt metadata, a=testonly wpt-pr: 28476 wpt-type: metadata
4bc07eb6d697e49b837a93ae9186f9e344e3f413: Bug 1705128 [wpt PR 28476] - Include custom properties on computed CSSStyleDeclaration, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Fri, 23 Apr 2021 10:16:26 +0000 - rev 577234
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705128 [wpt PR 28476] - Include custom properties on computed CSSStyleDeclaration, a=testonly Automatic update from web-platform-tests Include custom properties on computed CSSStyleDeclaration Since we need a "stable" list of custom properties for length() and item(), and we also need not-abysmal performance when calling those functions, this CL caches a vector with the variables names on ComputedStyle itself. In CSSComputedStyleDeclaration::item(), we check if the incoming index is in the range of the standard properties, and if so return the appropriate one. Otherwise, we're in the variable range (which is defined per spec to appear after the standard properties), and we'll fetch the list of variable names. Unfortunately the inclusion of custom properties requires a clean style, which means length()/item() now updates style/layout as needed. This might cause performance regressions, but I don't see a way around this. Note: ComputedStyle::StyleInheritedVariables/NonInheritedVariables were changed to return const pointers, as to not "leak mutability", which would have made it hard to invalidate the cache. (Nothing requires those return values to be non-const after StyleCascade anyway). Note: ComputedStyle::GetVariableNames() has pretty good test coverage in ComputedStyleTest already. Added a couple of new ones that target cache invalidation. Fixed: 949807 Change-Id: I6b181af5c4f025c4fd433de0a6ca221055c16693 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2822260 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#872446} -- wpt-commits: 72e8d5c2463fb0109f53a3a4357a998cb66d391b wpt-pr: 28476
f4aa099782dd2b5ea0a98e99e316dac7be83d486: Bug 1705132 [wpt PR 28478] - content-visibility: Ensure to dirty continuations on force unlocks., a=testonly
Vladimir Levin <vmpstr@chromium.org> - Fri, 23 Apr 2021 10:16:21 +0000 - rev 577233
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705132 [wpt PR 28478] - content-visibility: Ensure to dirty continuations on force unlocks., a=testonly Automatic update from web-platform-tests content-visibility: Ensure to dirty continuations on force unlocks. This patch ensures that we propagate a dirty bit from the continuations up the ancestor chain when we do a force unlock. In "regular" cases where we don't need to force unlock anything, we have layout containment which should prevent us from having continuations. R=ikilpatrick@chromium.org, kojii@chromium.org Fixed: 1197492 Change-Id: I2d8386e480c48c97e77875d3f8d73ad3d419c18c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2822899 Commit-Queue: vmpstr <vmpstr@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#872454} -- wpt-commits: 73eea9688017f191c7d68ca07049f968e543e022 wpt-pr: 28478
2f6e3bf089255de963545cfef220adb635a7a96d: Bug 1705129 [wpt PR 28477] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 14 Apr 2021 17:08:58 +0000 - rev 577232
Push 141827 by wptsync@mozilla.com at Sat, 24 Apr 2021 02:11:12 +0000
Bug 1705129 [wpt PR 28477] - Update wpt metadata, a=testonly wpt-pr: 28477 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip