7143cd0578a92d557e51976c537783f2f988fc9b: Bug 1636462 [wpt PR 23481] - device orientation: Try to remove flakiness from tests., a=testonly
Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> - Wed, 13 May 2020 09:48:44 +0000 - rev 531162
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636462 [wpt PR 23481] - device orientation: Try to remove flakiness from tests., a=testonly Automatic update from web-platform-tests device orientation: Try to remove flakiness from tests. https://crrev.com/c/2154389 ("[device-orientation] Simplifies tests by using EventWatcher") ended up introducing some Chromium-specific flakiness to most tests that started using EventWatcher, and the Mac bots in particular seem to trigger this flakiness very often. This comes from the fact that EventWatcher will continue watching for events until the end of the test, and the Blink implementation of the DeviceOrientation Event specification ends up emitting a non-standard null event whenever there are no more events to send. This event can end up being caught by EventWatcher, which correctly reports it as unexpected. For now, replace most usages of EventWatcher with a much simplified version of the waitForEvent() function removed in the CL above that only subscribes to events once. Bug: 816462, 1078298 Change-Id: I181219f2be19bba8a392c2bf64373f01df46c398 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2190273 Commit-Queue: Reilly Grant <reillyg@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Cr-Commit-Position: refs/heads/master@{#766988} -- wpt-commits: 54b6be43d7c1be3393ddf921703e60dee74e7777 wpt-pr: 23481
c18ec8257b9f3c61a2ce538734b91dd3b2d6e847: Bug 1636475 [wpt PR 23483] - Convert CLS source attribution integration tests to WPT., a=testonly
Steve Kobes <skobes@chromium.org> - Wed, 13 May 2020 09:48:39 +0000 - rev 531161
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636475 [wpt PR 23483] - Convert CLS source attribution integration tests to WPT., a=testonly Automatic update from web-platform-tests Convert CLS source attribution integration tests to WPT. Bug: 1053510 Change-Id: Ia1549ffa6d0c5d3e6f3dbdca79c83e4a66304852 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2189951 Commit-Queue: Steve Kobes <skobes@chromium.org> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#766956} -- wpt-commits: d0b09af9c467a2fa00dd84ec1d85037ee70a4fb3 wpt-pr: 23483
2445588003cd7c824255b3747dda2deb12c57b63: Bug 1634611 [wpt PR 23354] - Fugu: Add a permission for Screen Enumeration & Window Placement, a=testonly
Mike Wasserman <msw@chromium.org> - Wed, 13 May 2020 09:48:34 +0000 - rev 531160
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1634611 [wpt PR 23354] - Fugu: Add a permission for Screen Enumeration & Window Placement, a=testonly Automatic update from web-platform-tests Fugu: Add a permission for Screen Enumeration & Window Placement Add WINDOW_PLACEMENT content setting and permission enum values. Use this to gate access to the window.getScreens() experimental API. Wire up the permission request dialog and the page info bubble entry. Add WPT testdriver permission request support; test with granted&denied. Make RenderFrameHostImpl own ScreenEnumerationImpl; adjust bindings. (supports requesting permission for a given host and its origin) Limits getScreens() to Window contexts; which seems okay. Add UX&Privacy-chosen strings + sha hashes for translation screenshots. Test michaelwasserman.github.io/window-placement-demo with: chrome://flags#enable-experimental-web-platform-features OR $ chrome --enable-experimental-web-platform-features Bug: 994889, 897300 Test: Window Placement setting and permissions work for getScreens(). Change-Id: Iac38133c966d20d9a04c80d999091df16f9fd5c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2173342 Commit-Queue: Michael Wasserman <msw@chromium.org> Reviewed-by: Kamila Hasanbega <hkamila@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Reviewed-by: Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#766929} -- wpt-commits: 00b32d5054a9b61a451b7b99ae9c064935b770c6 wpt-pr: 23354
ebe0ad4219a29fb5227bf51f27c4b8972961335a: Bug 1636449 [wpt PR 23479] - Fix some path animation WPTs, a=testonly
Fredrik Söderqvist <fs@opera.com> - Wed, 13 May 2020 09:48:29 +0000 - rev 531159
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636449 [wpt PR 23479] - Fix some path animation WPTs, a=testonly Automatic update from web-platform-tests Fix some path animation WPTs These tests incorrectly assumed that getAttribute('d') would return the animated path data (string). Since there are differences between UAs with how animated path data can be accessed, add a helper (assert_animated_path_equals) that factors in these differences, and also allows to compare the result with an epsilon. This should make these tests pass in Gecko as well (and probably at least partially in WebKit). Bug: 735820 Change-Id: I2d0b0f3b0c34f95dbc75f576567e256231d55a11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2190632 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#766924} -- wpt-commits: c07eb06124e4fe32a6269b29b2521dad71189f73 wpt-pr: 23479
c75ce77b221d95e6c9c64b4fd7025d8e3951c914: Bug 1636322 [wpt PR 23470] - Fix a crash in custom built-in <input> element, a=testonly
Mason Freed <masonfreed@chromium.org> - Wed, 13 May 2020 09:48:24 +0000 - rev 531158
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636322 [wpt PR 23470] - Fix a crash in custom built-in <input> element, a=testonly Automatic update from web-platform-tests Fix a crash in custom built-in <input> element Prior to this CL, this code would cause an access violation crash: <script> customElements.define("my-input", class extends HTMLInputElement { }, { extends: "input" }); </script> <input is="my-input"> because the HTMLInputElement constructor purposely does not construct its input_type_ and input_type_view_ members until the parser calls the InitializeTypeInParsing() function. In the customized built-in element case, this was not getting called prior to attempting to set attributes. This bug was created with the [1] patch, which fixed several issues with custom element construction. [1] https://chromium.googlesource.com/chromium/src/+/7101418f85a0f17e4f9a35dfe3a9acff76340a93 Bug: 1078925, 1071059, 1024866 Change-Id: Id932d97d0d518bb28bdd2a7d846973a2a09e536d Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2188935 Commit-Queue: Mason Freed <masonfreed@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#766912} -- wpt-commits: e0dbe30737432a2f48d2ff3347705a1973679928 wpt-pr: 23470
e7567a2f9fbcfc2e982388bb2b84dbe94ac45762: Bug 1635928 [wpt PR 23442] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 08 May 2020 21:00:12 +0000 - rev 531157
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635928 [wpt PR 23442] - Update wpt metadata, a=testonly wpt-pr: 23442 wpt-type: metadata
1dbd10db1c1054c896e5e5cd24caae68ebe40f8d: Bug 1635928 [wpt PR 23442] - Improve webxr-test-api polyfill logic, a=testonly
Alexander Cooper <alcooper@chromium.org> - Wed, 13 May 2020 09:48:15 +0000 - rev 531156
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1635928 [wpt PR 23442] - Improve webxr-test-api polyfill logic, a=testonly Automatic update from web-platform-tests Improve webxr-test-api polyfill logic Now that Chromium no longer needs the polyfill to be created before the xr object is utilized, we can convert the loose promises into promise functions. This helps by allowing us to remove a duplicate check on the engine types in the relevant promises, and helps to make the loading behavior a bit more consistent. In addition, now that navigator.xr.test can be queried before creating the polyfill object, simplify the logic in webxr-test.js; this includes removing a no-longer-used guard for the old WebVR tests. Fixed: 1074452 Change-Id: Ieb52c412a0a4825387ef0b136cc4a85bbdb33191 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2185398 Reviewed-by: Brandon Jones <bajones@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#766908} -- wpt-commits: 699e916586620aeb96eb0554b3e5dc09035bf8ae wpt-pr: 23442
e8d82466ca218e703d2109edfa57f593021eba95: Bug 1636532 [wpt PR 23487] - Add timeout=long to PointerEvents idlharness test, a=testonly
Daniel Libby <dlibby@microsoft.com> - Wed, 13 May 2020 09:48:10 +0000 - rev 531155
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636532 [wpt PR 23487] - Add timeout=long to PointerEvents idlharness test, a=testonly Automatic update from web-platform-tests Add timeout=long to PointerEvents idlharness test Another test that shows symptoms of crbug.com/1047818, mark it timeout=long for now. Bug: 1079237 Change-Id: I7f95ea90d15a799e0ae07c4a6ebc32651c0e7a60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2190738 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#766893} -- wpt-commits: a39611cfa64ea8ee9172fcdb068c70470934726c wpt-pr: 23487
716ce44ad8a081d407caa06714a4b3fc263c0750: Bug 1636527 [wpt PR 23486] - Implement cross origin resource policy check , a=testonly
Bastien Orivel <eijebong@bananium.fr> - Wed, 13 May 2020 09:48:05 +0000 - rev 531154
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636527 [wpt PR 23486] - Implement cross origin resource policy check , a=testonly Automatic update from web-platform-tests Implement cross origin resource policy check I removed the window getter usage from those tests as servo does not support that yet. -- wpt-commits: c0981259b04a0d2dfd2c6ba397802d64b32c8974 wpt-pr: 23486
ae48b7d4543c9eec53af8fc3cb444f08296bddd7: Bug 1636288 [wpt PR 23467] - Test the sourceText of event handlers, a=testonly
Domenic Denicola <d@domenic.me> - Wed, 13 May 2020 09:48:00 +0000 - rev 531153
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636288 [wpt PR 23467] - Test the sourceText of event handlers, a=testonly Automatic update from web-platform-tests Test the sourceText of event handlers Follows https://github.com/whatwg/html/pull/5514. -- wpt-commits: af188628fbb56cbce2ba5c9ca418b5f465a64063 wpt-pr: 23467
da766ca50e082a89387305f78f68203fc36496ee: Bug 1636399 [wpt PR 23474] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 08 May 2020 18:26:31 +0000 - rev 531152
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636399 [wpt PR 23474] - Update wpt metadata, a=testonly wpt-pr: 23474 wpt-type: metadata
e1b279ab9036a08e94efc1c896c82e1bc14afd21: Bug 1636399 [wpt PR 23474] - Fix //fetch/metadata/preload.https.sub.html, a=testonly
Mike West <mkwst@google.com> - Wed, 13 May 2020 09:47:52 +0000 - rev 531151
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636399 [wpt PR 23474] - Fix //fetch/metadata/preload.https.sub.html, a=testonly Automatic update from web-platform-tests Fix //fetch/metadata/preload.https.sub.html (#23474) We're currently exiting the test before `fetch()` resolves due to using `step_func_done()` rather than `step_func()`. -- wpt-commits: dbf24d19488c5498b099c48540c62a48695b2b73 wpt-pr: 23474
e0cb1fb269f4c6f00f6cecb435ecb8a51e5c92a0: Bug 1636258 [wpt PR 23465] - [css-pseudo] Add test with ::marker web animations, a=testonly
Oriol Brufau <obrufau@igalia.com> - Wed, 13 May 2020 09:47:47 +0000 - rev 531150
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636258 [wpt PR 23465] - [css-pseudo] Add test with ::marker web animations, a=testonly Automatic update from web-platform-tests [css-pseudo] Add test with ::marker web animations An early return in StyleResolver::PseudoStyleForElementInternal used to prevent a ::marker with no styles from being affected by web animations. That early return was already removed in r765965 so the problem has been fixed, this patch just adds a test. BUG=1063283 TEST=external/wpt/css/css-pseudo/marker-animate.html Change-Id: I72a1286e9c3fbd200f46cb3172760f5aaedda18b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2188391 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#766835} -- wpt-commits: d929bede252f5d1a51fdad2bcfca8839e7e436ac wpt-pr: 23465
07c15b19a9b95e5fcdbe79d09f57134b0753c932: Bug 1636435 [wpt PR 23476] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 08 May 2020 15:44:53 +0000 - rev 531149
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636435 [wpt PR 23476] - Update wpt metadata, a=testonly wpt-pr: 23476 wpt-type: metadata
73514f66f8950d20c7c7e5b9e0c3fd64c11ac53f: Bug 1636435 [wpt PR 23476] - Improve WebAssembly.Memory tests, a=testonly
Ms2ger <Ms2ger@gmail.com> - Wed, 13 May 2020 09:47:39 +0000 - rev 531148
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636435 [wpt PR 23476] - Improve WebAssembly.Memory tests, a=testonly Automatic update from web-platform-tests Move assert_Memory, assert_ArrayBuffer into a shared file. -- Share code between assert_Memory, assert_ArrayBuffer. -- Split tests for shared memory out of the main file. -- wpt-commits: 4ec47c29ffeccedab03bf6dc22a3b4507fac4865, a6b683ff6af2b83e7c4a2e49307c9ea3bf6c8ca1, 943b6ed25e66b68399ec0cfb2327d8437614c424 wpt-pr: 23476
803e71597e6b85e280b3725f51f030d3cbee1dbf: Bug 1636358 [wpt PR 23473] - Reland: "[FlexNG] Make ComputeMinMaxSizes cache more precise.", a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Wed, 13 May 2020 09:47:34 +0000 - rev 531147
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1636358 [wpt PR 23473] - Reland: "[FlexNG] Make ComputeMinMaxSizes cache more precise.", a=testonly Automatic update from web-platform-tests Reland: "[FlexNG] Make ComputeMinMaxSizes cache more precise." This is a reland of 044aeb3ed3364905cc185d67eb947c7ca3c13741 The initial patch was reverted due to an MSAN failure. This was caused by MinMaxSizesResult::depends_on_percentage_block_size not being initialized within the NGFieldsetLayoutAlgorithm. This reland always initialises depends_on_percentage_block_size to false. This also adds some documentation not present in the initial patch. Original change's description: Previously our cache was imprecise, we recalculate our min/max sizes when we didn't strictly need to, as we didn't know if we'd have a %-block-size replaced element beneath us. This patch changes ComputeMinMaxSizes to return a MinMaxSizesResult (instead of just MinMaxSizes). This contains an additional bit of information to indicate if this sub-tree depended on the %-block-size given to it. For most things, this will return false. For legacy layout roots we always assume that they have children which depend on the %-block-size (and why we initialize: intrinsic_logical_widths_depends_on_percentage_block_size_ to true). Along with this change, the cache changes in the following way: - We store an addition bit of information on LayoutBox to store the bit of information from ComputeMinMaxSizes. - We calculate the %-block-size for our children up-front, this means each of the algorithms don't have to do this. - With these changes, the cache can now hit, when the %-block-size given to us changes. \o/ Bug: 845235 Change-Id: I6c7e79c5ad787291ba2eeb4d1eebb5437f1934fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2189620 Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#766826} -- wpt-commits: ee3228e0cb8b0abc1a6e487345ece9fe5868e321 wpt-pr: 23473
4d2c3e4aa7e58dfc65cea8b45ce2a6eb1d428331: Bug 1625663 [wpt PR 22507] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 08 May 2020 04:11:49 +0000 - rev 531146
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1625663 [wpt PR 22507] - Update wpt metadata, a=testonly wpt-pr: 22507 wpt-type: metadata
84ec9c8665947bc5c8f8e159cda1567034b8744d: Bug 1625663 [wpt PR 22507] - Raw Clipboard: Implement read., a=testonly
Darwin Huang <huangdarwin@chromium.org> - Wed, 13 May 2020 09:47:25 +0000 - rev 531145
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1625663 [wpt PR 22507] - Raw Clipboard: Implement read., a=testonly Automatic update from web-platform-tests Raw Clipboard: Implement read. Implement Raw Clipboard interface for reading arbitrary data. Also, implements mock interfaces for automated content_shell/WPT tests. The browser-side change is more simple than the equivalent Raw Write and Raw Format CLs due to platform-specific code already being handled in ui::Clipboard::read(). The Raw Clipboard API is only accessible if the user turns on the Raw Clipboard feature flag, and explicitly provides permission via permission prompt. These checks are contained in both the browser and renderer. Design Doc: https://tinyurl.com/raw-clipboard-access-design Bug: 897289 Change-Id: Ic5a778cf4c6421ea15bf44faebf08d23e3b39b5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2107156 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#766694} -- wpt-commits: df7fc2ece226676b8398ece13ddfd31b4f1eca5c wpt-pr: 22507
1e8c846597a02dfb67f05936eaef1f3fbc5c66e8: Bug 1634781 [wpt PR 23368] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 08 May 2020 03:49:35 +0000 - rev 531144
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1634781 [wpt PR 23368] - Update wpt metadata, a=testonly wpt-pr: 23368 wpt-type: metadata
8745c436c63c9bcc767b3bc90e6137824c2522cf: Bug 1634781 [wpt PR 23368] - Move mouse pointerevents compat events to wpt, a=testonly
Navid Zolghadr <nzolghadr@chromium.org> - Wed, 13 May 2020 09:47:17 +0000 - rev 531143
Push 37435 by apavel@mozilla.com at Wed, 20 May 2020 15:28:23 +0000
Bug 1634781 [wpt PR 23368] - Move mouse pointerevents compat events to wpt, a=testonly Automatic update from web-platform-tests Move mouse pointerevents compat events to wpt Change-Id: Ie5b8bdbb36e23ddee4d2445502971b9a5c14d2a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176104 Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Auto-Submit: Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#766684} -- wpt-commits: a3ffd5bd3a13aae75ca728c1744fa548dfa453e3 wpt-pr: 23368
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip