b7e0c8136e19666494640a8f928e2edbc78f2e29: Bug 1631413 [wpt PR 23112] - Wasm: test SharedArrayBuffer-ness in another way, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 28 Apr 2020 11:36:11 +0000 - rev 527558
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631413 [wpt PR 23112] - Wasm: test SharedArrayBuffer-ness in another way, a=testonly Automatic update from web-platform-tests Wasm: test SharedArrayBuffer-ness in another way (#23112) -- wpt-commits: 6a1b15e5d699a00d58844b53e8c18d368169018d wpt-pr: 23112
cdfb07b2861aae38c97d239bbcf268faf2736e7e: Bug 1632031 [wpt PR 23161] - SignedExchange: Extend timeout of two tests, a=testonly
Kunihiko Sakamoto <ksakamoto@chromium.org> - Tue, 28 Apr 2020 11:36:06 +0000 - rev 527557
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1632031 [wpt PR 23161] - SignedExchange: Extend timeout of two tests, a=testonly Automatic update from web-platform-tests SignedExchange: Extend timeout of two tests This extends timeout of two WPTs that are flakily timing out on bots: - sxg-reporting-navigation-parse_error.tentative.html - sxg-referrer-remote-physical-remote-logical.tentative.https.html Bug: 1067502,1067264 Change-Id: I94a5fdaa0f4e8cf810438c8fba370300d4f72195 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159386 Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#761303} -- wpt-commits: c4d9e7b35b0b011c4f7fc15d618261500efa8c8d wpt-pr: 23161
94668bcce89dcac17b3f09ed67b4b15840102763: Bug 1587902 [wpt PR 19632] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 02:47:51 +0000 - rev 527556
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1587902 [wpt PR 19632] - Update wpt metadata, a=testonly wpt-pr: 19632 wpt-type: metadata
fdfdeaafaa3ea6cd8883bc904cd1fdab533b22e9: Bug 1587902 [wpt PR 19632] - Scripts moved between documents, a=testonly
hiroshige-g <hiroshige@chromium.org> - Tue, 28 Apr 2020 11:35:58 +0000 - rev 527555
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1587902 [wpt PR 19632] - Scripts moved between documents, a=testonly Automatic update from web-platform-tests Scripts moved between documents (#19632) This follows the changes in https://github.com/whatwg/html/pull/2673, but also tests the issue at https://github.com/whatwg/html/issues/2137 in favor of the current spec. Co-Authored-By: Domenic Denicola <d@domenic.me> -- wpt-commits: 299dd665683c2c5a4896bfb7727d8666aa6bba89 wpt-pr: 19632
aa9237f94e6fa8451dc7ce09471a6e80d09b8323: Bug 1631948 [wpt PR 23153] - Fix Webxr WPTs, a=testonly
Alexander Cooper <alcooper@chromium.org> - Tue, 28 Apr 2020 11:35:53 +0000 - rev 527554
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631948 [wpt PR 23153] - Fix Webxr WPTs, a=testonly Automatic update from web-platform-tests Fix Webxr WPTs The "is webkit" heuristic only checks that self.internals exists; however, this is also true on chromium. Chromium however does not have an "internals.xrTest", this expands the "is webkit" heuristic to also account for the presence of "internals.xrTest" and thus ensure chromium tests run Fixed: 1072929 Change-Id: Ieba043ba1634b393905e4494d0c59294aa6df12b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2159320 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Auto-Submit: Alexander Cooper <alcooper@chromium.org> Reviewed-by: Brandon Jones <bajones@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#761158} -- wpt-commits: ef350cb9bd09615e8519a6d3ce08b478e4961207 wpt-pr: 23153
880e5158d0f65527e1b61be6e5850316128ba906: Bug 1631731 [wpt PR 23134] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Apr 2020 00:25:04 +0000 - rev 527553
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631731 [wpt PR 23134] - Update wpt metadata, a=testonly wpt-pr: 23134 wpt-type: metadata
1fb5e8dca04615104c2c4084d4522b9542b71b28: Bug 1631731 [wpt PR 23134] - [@property] Set status to 'test' and move tests to WPT, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Tue, 28 Apr 2020 11:35:45 +0000 - rev 527552
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631731 [wpt PR 23134] - [@property] Set status to 'test' and move tests to WPT, a=testonly Automatic update from web-platform-tests [@property] Set status to 'test' and move tests to WPT Bug: 973830 Change-Id: I5d950496834ab17dc8615335c9c4ae25f2a4179b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157528 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#761157} -- wpt-commits: 8ab9b393636f35a1ddeb0526483b9c03013a4f98 wpt-pr: 23134
85717ca941fff6abca6893202f0fd26bc0aad518: Bug 1631100 [wpt PR 23075] - Set up py3-only tools/quic and its venv, a=testonly
Robert Ma <robertma@chromium.org> - Tue, 28 Apr 2020 11:35:40 +0000 - rev 527551
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631100 [wpt PR 23075] - Set up py3-only tools/quic and its venv, a=testonly Automatic update from web-platform-tests Set up py3-only tools/quic and its venv (#23075) * [quic] Set up py3-only tools/quic and its venv This does not include the actual server, but only sets up the skeleton: * Introduce a "py3only" to commands.json * Create the skeleton of tools/quic and set up its venv The plan is to have `wpt serve` call `wpt servequic` (behind a flag). For more details, see https://github.com/web-platform-tests/rfcs/blob/master/rfcs/quic.md * Squashed 'tools/third_party/aioquic/' content from commit 88f258ae47 git-subtree-dir: tools/third_party/aioquic git-subtree-split: 88f258ae47b7ec85de5ecf4104665054b969a9bb -- wpt-commits: 4b870dfffeb7031d3657af7a950dd0ea1304bf10 wpt-pr: 23075
9cd02d20cdc59565fd86ad4801e375e69f396d1a: Bug 1631115 [wpt PR 23078] - Tweak lints and checks for tools/quic, a=testonly
Robert Ma <robertma@chromium.org> - Tue, 28 Apr 2020 11:35:33 +0000 - rev 527550
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631115 [wpt PR 23078] - Tweak lints and checks for tools/quic, a=testonly Automatic update from web-platform-tests [lint] Add support for QUIC handlers and tests * handlers: .quic.py files are Python 3-only so don't try to parse them. * tests: add "quic" as a valid kind of metadata (note that manifest support hasn't been implemented yet). -- Skip tools/quic in py27-flake8 It contains code invalid in Python 2. Drive-by: rename py36-flake8.ini to py3-flake8.ini as it's used by multiple Python 3 versions. -- wpt-commits: 8cdf17f2eca3a8fab82eccbe907627f2052382bd, 1d787b148b6bc65324746339d903c84e653e8ac5 wpt-pr: 23078
c85995332e2fd7a9dc2271bba2f2eb76a8458473: Bug 1631891 [wpt PR 23149] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 21 Apr 2020 20:34:22 +0000 - rev 527549
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631891 [wpt PR 23149] - Update wpt metadata, a=testonly wpt-pr: 23149 wpt-type: metadata
826abddf272b4ba1252ef4482454c96c504981d4: Bug 1631891 [wpt PR 23149] - Rename a bunch of older idlharness test, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:35:25 +0000 - rev 527548
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631891 [wpt PR 23149] - Rename a bunch of older idlharness test, a=testonly Automatic update from web-platform-tests Rename a bunch of older idlharness test (#23149) The modern naming convention seems to be to have the test include the word 'idlharness' in some way, whereas 'interfaces' was the old version. -- wpt-commits: e00d15c0e09f84bb65588fff9546f80c3721f04b wpt-pr: 23149
1b2a09e3b4726cb90d9dcfacf7999dd4a1e50d80: Bug 1631732 [wpt PR 23135] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 21 Apr 2020 21:53:08 +0000 - rev 527547
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631732 [wpt PR 23135] - Update wpt metadata, a=testonly wpt-pr: 23135 wpt-type: metadata
11570b6989c7dd77a05a42ce1a7af44af0e6fc99: Bug 1631732 [wpt PR 23135] - [@property] Determine the registration, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Tue, 28 Apr 2020 11:35:17 +0000 - rev 527546
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631732 [wpt PR 23135] - [@property] Determine the registration, a=testonly Automatic update from web-platform-tests [@property] Determine the registration The current behavior for dealing with multiple registrations on the same custom property was highly temporary, and not based on any spec. The spec has since been updated to describe how it should work: in short, registrations originating from CSS.registerProperty are stored independently from those originating from @property, and CSS.registerProperty-registrations (if present) win over @property- registrations. Changes in this CL: - Separates storage for CSS.registerProperty-registrations (registered_properties_) and @property-registrations (declared_properties_). The old code put @property registrations in the same map as CSS.registerProperty-registrations, and only if no registration exited already. (Meaning for example that the first @property seen would win---opposite of how it's spec'd to work now). - Determines the registration [1] correctly. I.e. first checks the the CSS.registerProperty-registrations, and the @property ones. - Adds an iterator which yields the currently active registrations across both registration types. (I wanted to do this separately, but initial values won't work properly without it, and there's a test that relies heavily on that being functional). Note that it's not explicitly stated in the spec that the storage for the two registration types shall be separate, but that _is_ the background for the current spec text on the subject. The rationale is that it makes it easier to reason about which registration is the current one when @property rules can appear and disappear via JS. It's also expected that CSS.unregisterProperty will be added in the future, making the situation even more unstable. [1] https://drafts.css-houdini.org/css-properties-values-api-1/#determining-registration Bug: 973830 Change-Id: I69b48629034b333ebed5d374f943d08b39579334 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2157071 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#761075} -- wpt-commits: 7aa1b761a317d924763915d2505f3a500659b47f wpt-pr: 23135
e4651ad8076551d9f051e488bb71d4e68416e931: Bug 1630709 [wpt PR 23026] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 21 Apr 2020 21:41:11 +0000 - rev 527545
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630709 [wpt PR 23026] - Update wpt metadata, a=testonly wpt-pr: 23026 wpt-type: metadata
b344b9215d483595ac5726aaf149e28dbb387024: Bug 1630709 [wpt PR 23026] - CookieStore: Add validation behavior for __Host- prefixed cookies, a=testonly
Ayu Ishii <ayui@chromium.org> - Tue, 28 Apr 2020 11:35:09 +0000 - rev 527544
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630709 [wpt PR 23026] - CookieStore: Add validation behavior for __Host- prefixed cookies, a=testonly Automatic update from web-platform-tests CookieStore: Add validation behavior for __Host- prefixed cookies This change adds the following checks for "__Host-" prefixed cookies: 1. Disallows overwriting with an explicit domain 2. Disallows non "/" path This behavior is mentioned in the spec here [1]. Creating a cookie that violates this will cause a crash without this change. [1] https://wicg.github.io/cookie-store/#prefixes Change-Id: I20968f11759019921aa7a6b37602878a17b091ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151825 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#760776} -- wpt-commits: e731ebbe61dc7cd861633585c704fb59bde64b9f wpt-pr: 23026
7d0fd0d31d2b3bb69ac69f7f2bacfa5d3b8b1f92: Bug 1631148 [wpt PR 23082] - Screen Enumeration: Add a placeholder Screen.id to replace Screen.name, a=testonly
Mike Wasserman <msw@chromium.org> - Tue, 28 Apr 2020 11:35:04 +0000 - rev 527543
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631148 [wpt PR 23082] - Screen Enumeration: Add a placeholder Screen.id to replace Screen.name, a=testonly Automatic update from web-platform-tests Screen Enumeration: Add a placeholder Screen.id to replace Screen.name Use placeholder ordinal ids for now (0, 1, 2, ...); update tests. TODO: generate per-origin UUIDs that reset when cookies are deleted Test Screen.id values returned via window.getScreens() with: chrome://flags#enable-experimental-web-platform-features OR $ chrome --enable-blink-features=ScreenEnumeration Try https://michaelwasserman.github.io/window-placement-demo Bug: 994889 Test: Automated, Screen.id placeholder values Change-Id: I0c5b18b92fef251211822f3473ea85472a7ee945 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155113 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#761040} -- wpt-commits: f8d36b93adcfb21622c935a77427bf99caf3d1e3 wpt-pr: 23082
16f63baa9864fd619c7b2d4c7a81a8d3dc1b254e: Bug 1631881 [wpt PR 23147] - Update interfaces/hit-test.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 28 Apr 2020 11:34:54 +0000 - rev 527542
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1631881 [wpt PR 23147] - Update interfaces/hit-test.idl, a=testonly Automatic update from web-platform-tests Update interfaces/hit-test.idl (#23147) Note: This file was recently manually updated in commit 8a9e492c5b. This commit may revert some of those changes. Source: https://github.com/tidoust/reffy-reports/blob/d3a60b6/ed/idl/hit-test.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/677821722 -- wpt-commits: 3681334e2d310aca4421575b8f307eda56cf2967 wpt-pr: 23147
6a7be38cb8f33b5ac5eb4490b57c7cf657f9b242: Bug 1630745 [wpt PR 23032] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 21 Apr 2020 21:12:54 +0000 - rev 527541
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630745 [wpt PR 23032] - Update wpt metadata, a=testonly wpt-pr: 23032 wpt-type: metadata
8e727e285adbc143fe0aae366ef688954921ce74: Bug 1630745 [wpt PR 23032] - Animations modified with setKeyframes must not mask !important, a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Tue, 28 Apr 2020 11:34:46 +0000 - rev 527540
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630745 [wpt PR 23032] - Animations modified with setKeyframes must not mask !important, a=testonly Automatic update from web-platform-tests Animations modified with setKeyframes must not mask !important CSS declarations that are !important have higher priority in the cascade than animation effects. Unfortunately the information about which declarations were and weren't important is lost once the StyleCascade disappears. Specifically, it's not stored on the ComputedStyle. This causes a problem (once again) for the base computed style optimization, since we can't naively add animation effects on top of the base anymore. We might be overwriting something in the base that was important. The previous attempt at fixing this (flag on ElementAnimations) doesn't work properly. For example, it fails to detect the case where an animation initially doesn't conflict with important declarations, but then suddenly does via setKeyframes. To solve this, this CL stores a bitset containing information about important declarations alongside the base ComputedStyle on ElementAnimations. When we're considering whether the base can be used or not, we then check if there's any animation matching the set of important declarations. Persisting that many bits is slightly uncomfortable, but the only viable alternative I see is disabling the optimization when *any* important declaration exists in the base, which is probably a worse option. Sidenote: Initially I tried to always use the base, even when there were conflicts with important declarations. The bitset of important declarations is effectively a set of animations to be skipped, so we should still be able to use the base if we just don't apply the properties present in the set. However, it unfortunately didn't work due to visited/unvisited colors being animated together (crbug.com/1062217). Bug: 552085 Change-Id: I39e2879af8a858ce1bd97eaa2ceb6e222591df79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152449 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#761034} -- wpt-commits: 9f16de83abdee864d6dafebbacc298b08964750d wpt-pr: 23032
7c786601421dabc1082e7dae5f3411ef95144b53: Bug 1630699 [wpt PR 23022] - Replace assert_precondition with assert_implements in vibration/, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Tue, 28 Apr 2020 11:34:41 +0000 - rev 527539
Push 37368 by btara@mozilla.com at Fri, 01 May 2020 21:45:51 +0000
Bug 1630699 [wpt PR 23022] - Replace assert_precondition with assert_implements in vibration/, a=testonly Automatic update from web-platform-tests Replace assert_precondition with assert_implements in vibration/ (#23022) assert_precondition is deprecated (see https://github.com/web-platform-tests/rfcs/blob/master/rfcs/assert_precondition_rename.md). Since navigator.vibrate is not an OPTIONAL part of the Vibration API spec, this test should use assert_implements. -- wpt-commits: 440e3632f10aadb0fc0f90c923ca6b6467887fd8 wpt-pr: 23022
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip