ba11e3c978ee7e8bbd7862f775ddd72e13b322ff: Bug 1527153 [wpt PR 15330] - Make stability checks provide an explicit message for duplicate test names, a=testonly
James Graham <james@hoppipolla.co.uk> - Tue, 19 Feb 2019 14:39:06 +0000 - rev 461358
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527153 [wpt PR 15330] - Make stability checks provide an explicit message for duplicate test names, a=testonly Automatic update from web-platform-tests Make stability checks provide an explicit message for duplicate test names -- wpt-commits: 23008e948bff4c245148cfcda2ebaa72149a2bb1 wpt-pr: 15330
493a1e6d8fd23f7da345e00b1fc10f335633d968: Bug 1527149 [wpt PR 15328] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 13 Feb 2019 13:55:20 +0000 - rev 461357
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527149 [wpt PR 15328] - Update wpt metadata, a=testonly wpt-pr: 15328 wpt-type: metadata
957e02354f5eb4a8873a8ebb6fe3d2023ec1f025: Bug 1527149 [wpt PR 15328] - HTML: noopener keyword is tokenized, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 19 Feb 2019 14:39:00 +0000 - rev 461356
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527149 [wpt PR 15328] - HTML: noopener keyword is tokenized, a=testonly Automatic update from web-platform-tests HTML: noopener keyword is tokenized See https://github.com/whatwg/html/pull/4079. -- wpt-commits: 6d9e199e99ce76bafb4d31a58641e5a2591c9587 wpt-pr: 15328
6e9a763bcb5f3f6ef94ceed37805602216ad24f9: Bug 1526827 [wpt PR 15294] - Update mozprocess to 1.0.0, a=testonly
pyup-bot <github-bot@pyup.io> - Tue, 19 Feb 2019 14:38:58 +0000 - rev 461355
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526827 [wpt PR 15294] - Update mozprocess to 1.0.0, a=testonly Automatic update from web-platform-tests Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- Update mozprocess from 0.26 to 1.0.0 -- wpt-commits: 9a874520787308eecb14d85399cb5184efaf99ec, 999c546d4958eb649a71f0339563218a22f6d281, e032140d4ba4954c0704356f4848cc8f1d2dd590, ad09e7414f098c7833a65d336f01e76ba8c1dc15, a54f2b6ed9445d74fded895c45b561b1e7fd9314, 47bb668028ce2b7f6e564b47aee7ed12ce720532, f55469ea2fe1ed49f6b3f2d9701b793fc051bb67, 78c2264a4d9b28e89070670d6a73df470ae45aaf, 725876f98dc3fe1dd86c131b73724ac0e0a41147 wpt-pr: 15294
d979f778d2f893690b3d7ec501d0b8c36c346342: Bug 1526746 [wpt PR 15284] - [css-grid] Overflow should be computed with the actual logical bottom, a=testonly
Javier Fernandez <jfernandez@igalia.com> - Tue, 19 Feb 2019 14:38:56 +0000 - rev 461354
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526746 [wpt PR 15284] - [css-grid] Overflow should be computed with the actual logical bottom, a=testonly Automatic update from web-platform-tests [css-grid] Overflow should be computed with the actual logical bottom In order to compute the 'auto' height of the grid container, we set temporarily a value based on the tracks' size. We can see this value as a kind of 'intrinsic height'. Then, we call to the UpdateLogicalHeight function to finally compute the grid container's actual logical height. In order to compute the overflow area in the grid container we should use the result of the ClientLogicalBottom function. However, we were retrieving this value just after setting the tracks-based temporary height, and before computing the actual logical height. The consequence of this wrong logic is that empty grid areas may affect the result of the ClientLogicalBottom and, as it's described in the bug, conclude that there is a content overflow in the grid container, even if such container has no grid items at all. Since the grid itself is not a box, it can't contribute to the grid container's content size; instead, its grid items should. This change ensures that we always use the actual grid container's logical bottom to properly compute the overflow area. Bug: 928885 Change-Id: I05f86fbce06a83c0dbc0d5389bf0416763f8588a Reviewed-on: https://chromium-review.googlesource.com/c/1459620 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#630735} -- wpt-commits: aa6f52fc7b99559377c760a550e842438efa91a1 wpt-pr: 15284
0dec93e4ebd2ba049322e204eae1b330ff174a58: Bug 1527143 [wpt PR 15317] - Update mozversion to 2.1.0, a=testonly
pyup.io bot <github-bot@pyup.io> - Tue, 19 Feb 2019 14:38:54 +0000 - rev 461353
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527143 [wpt PR 15317] - Update mozversion to 2.1.0, a=testonly Automatic update from web-platform-tests Update mozversion from 1.5 to 2.1.0 (#15317) -- wpt-commits: edbcef5df62a561d82a3303cb2044e2352bf4020 wpt-pr: 15317
eca5d888e47f18532896f5671d22f463fab67bf5: Bug 1527139 [wpt PR 15188] - HTML: target=_blank implies noopener; opener support, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 19 Feb 2019 14:38:52 +0000 - rev 461352
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527139 [wpt PR 15188] - HTML: target=_blank implies noopener; opener support, a=testonly Automatic update from web-platform-tests HTML: target=_blank implies noopener; opener support (#15188) For https://github.com/whatwg/html/pull/4330. -- wpt-commits: e81ca209b45fbe73c1bb7a20e1c7af51ef46258b wpt-pr: 15188
a489a398a5e73a15d8c395f79168e4946e678b99: Bug 1526893 [wpt PR 15323] - Remove my deadname from everywhere except tools/third_party, a=testonly
Sam Sneddon <me@gsnedders.com> - Tue, 19 Feb 2019 14:38:49 +0000 - rev 461351
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526893 [wpt PR 15323] - Remove my deadname from everywhere except tools/third_party, a=testonly Automatic update from web-platform-tests Remove Sam's deadname from everywhere except tools/third_party (#15323) -- wpt-commits: 91b5bfb7a26098545b0d317ec2547dbe52d8ddd7 wpt-pr: 15323
da00dfebf895b0652a307efbd210ecf680c97ff3: Bug 1526730 [wpt PR 15280] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 13 Feb 2019 13:40:10 +0000 - rev 461350
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526730 [wpt PR 15280] - Update wpt metadata, a=testonly wpt-pr: 15280 wpt-type: metadata
c4da5566b9663c79809d741bc7ca21ff28653ec9: Bug 1526730 [wpt PR 15280] - [Animation Worklet] Upstream web tests (related to setting values) to WPT, a=testonly
Jordan Taylor <jortaylo@microsoft.com> - Tue, 19 Feb 2019 14:38:44 +0000 - rev 461349
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526730 [wpt PR 15280] - [Animation Worklet] Upstream web tests (related to setting values) to WPT, a=testonly Automatic update from web-platform-tests [Animation Worklet] Upstream web tests (related to setting values) to WPT web_tests/animations/animationworklet/worklet-animation-set-keyframes.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-keyframes.https.html web_tests/animations/animationworklet/worklet-animation-set-keyframes-expected.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-keyframes-ref.html web_tests/animations/animationworklet/worklet-animation-set-timing.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-timing.https.html web_tests/animations/animationworklet/worklet-animation-set-timing-expected.html -> web_tests/external/wpt/animation-worklet/worklet-animation-set-timing-ref.html Bug: 915352 Change-Id: I95f69fcfaea64b8d779e136facb87b6f5c16c27c Reviewed-on: https://chromium-review.googlesource.com/c/1459069 Reviewed-by: Yi Gu <yigu@chromium.org> Commit-Queue: Jordan Taylor <jortaylo@microsoft.com> Cr-Commit-Position: refs/heads/master@{#630554} -- wpt-commits: 8320b02221923df3b7813b13333fb4fe8890a0fe wpt-pr: 15280
8b67c6a2fd48ee4d3604e9973564c681e08a8e0d: Bug 1526643 [wpt PR 15129] - Fix remaining preload tests flaking on wpt.fyi, a=testonly
Kunihiko Sakamoto <ksakamoto@chromium.org> - Tue, 19 Feb 2019 14:38:42 +0000 - rev 461348
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526643 [wpt PR 15129] - Fix remaining preload tests flaking on wpt.fyi, a=testonly Automatic update from web-platform-tests Fix remaining preload tests flaking on wpt.fyi This is a follow-up to https://github.com/web-platform-tests/wpt/pull/15075. https://crrev.com/c/1436777 successfully fixed the wpt.fyi flakiness for link-header-preload-srcset.tentative.html and link-header-preload-nonce.html. This patch fixes that for the remaining preload tests. - Use step_timeout instead of dummy.js?pipe=trickle, because dummy.js?pipe=trickle may be loaded from cache with no delay. - Replace verifyNumberOfDownloads() with - verifyNumberOfResourceTimingEntries() if possible - A new helper function verifyLoadedAndNoDoubleDownload() that doesn't fail if the resource was already cached before running the test. Bug: 922343 Change-Id: Ia9b7c4bd49dd76463df4607349fe4f935e5410d0 Reviewed-on: https://chromium-review.googlesource.com/c/1442020 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#629029} -- wpt-commits: eb5aa0038ee7a938beabbe4c732a685af2581dbc wpt-pr: 15129
8d84d8255986a0b1e5a3abe604d60557307fa2f6: Bug 1526644 [wpt PR 14946] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 13 Feb 2019 13:30:40 +0000 - rev 461347
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526644 [wpt PR 14946] - Update wpt metadata, a=testonly wpt-pr: 14946 wpt-type: metadata
cb5e210da1d833707d09aa6d417641fc8c52b11f: Bug 1526644 [wpt PR 14946] - Initial support for WorkletAnimation.playbackRate, a=testonly
Olga Gerchikov <gerchiko@microsoft.com> - Tue, 19 Feb 2019 14:38:37 +0000 - rev 461346
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526644 [wpt PR 14946] - Initial support for WorkletAnimation.playbackRate, a=testonly Automatic update from web-platform-tests Initial support for WorkletAnimation.playbackRate Changes for scroll-linked worklet animations will come in a separate pull request. Bug: 852475 Change-Id: Ie6dd14242797cbc14a7e1e377f23c3dda174fe15 Reviewed-on: https://chromium-review.googlesource.com/c/1423537 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com> Cr-Commit-Position: refs/heads/master@{#628800} -- wpt-commits: 9d1de21ddfa4338cfac14a887622b98207efe247 wpt-pr: 14946
9e5d55b9cba119908c4790871d2c3b6cc5aa6522: Bug 1526728 [wpt PR 15279] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 13 Feb 2019 13:25:21 +0000 - rev 461345
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526728 [wpt PR 15279] - Update wpt metadata, a=testonly wpt-pr: 15279 wpt-type: metadata
d57f0aa7c8a7004d4a638c863255ee3ea2f45fcd: Bug 1526728 [wpt PR 15279] - [animation-worklet] Basic pause implementation (reland), a=testonly
Majid Valipour <majidvp@chromium.org> - Tue, 19 Feb 2019 11:46:49 +0000 - rev 461344
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1526728 [wpt PR 15279] - [animation-worklet] Basic pause implementation (reland), a=testonly Automatic update from web-platform-tests [animation-worklet] Basic pause implementation (reland) Pausing worklet animation now holds the time. This works as expected for main thread animations. Implementing this for composited worklet animations will be done in a follow up patch. Major changes: - Add and expose pause() method pausing the animation. - Introduce hold_time that is used when animation is paused. - Rework how current time is computed, it is now closer to regular animations i.e., we either compute it based on "start time and timeline.currentTime" or use "hold time". - Instead of setting start time we now set the current time which then works backward to compute either the start time or the hold time based on the animation state. - When transitioning animation play state, we now always set the current time. Previously this was adhoc and inconsistent. - Introduce has_started_ to differentiate when playing an animation for the first time vs playing it from pause. - Update playback_rate related calculation to use new logic. Relanding: Original CL was reverted here [1]. Took the following steps to address this: - Address flakiness in unit test by using more accurate error value matching other tests. - Fix flakiness in layout test (worklet-animation-pause.https.html) by using startTime and waiting for time to actually advance working around pre-existing animation clock issue [2]. Also got rid of an invalid state transition from pause->idle. [1] https://chromium-review.googlesource.com/c/chromium/src/+/1434815 [2] http://crbug.com/785940 TEST: - wpt/animation-worklet/worklet-animation-pause.https.html: js test for basic current time calculations - wpt/animation-worklet/worklet-animation-pause-immediately.https.html: reftest for basic pause - wpt/animation-worklet/worklet-animation-pause-result.https.html: reftest for pause/resume. - WorkletAnimationTest.PausePlay: unit test for basic state transition and time calc Bug: 821910, Change-Id: I11fd2960443081be81055904d6d56a2abc3282f5 Reviewed-on: https://chromium-review.googlesource.com/c/1456640 Reviewed-by: Majid Valipour <majidvp@chromium.org> Reviewed-by: Yi Gu <yigu@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#630548} -- wpt-commits: 345300fad3945a5f1441fb2b2001109ca48f36e8 wpt-pr: 15279
cd859f2c535d48b4fc1208970b6f7025f99d66d0: Bug 1527046 [wpt PR 15306] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 13 Feb 2019 13:19:38 +0000 - rev 461343
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527046 [wpt PR 15306] - Update wpt metadata, a=testonly wpt-pr: 15306 wpt-type: metadata
215f68d94d86a724e0620aec714b61d92d2903a5: Bug 1527046 [wpt PR 15306] - [Payment Request] Add Web Platform Tests for hasEnrolledInstrument()., a=testonly
Danyao Wang <danyao@chromium.org> - Tue, 19 Feb 2019 11:46:44 +0000 - rev 461342
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527046 [wpt PR 15306] - [Payment Request] Add Web Platform Tests for hasEnrolledInstrument()., a=testonly Automatic update from web-platform-tests [Payment Request] Add Web Platform Tests for hasEnrolledInstrument(). The failing expectations are required because hasEnrolledInstrument() is not yet turned on by default in Blink. These tests pass when running Chrome with --enable-features=PaymentRequestHasEnrolledInstrument. Bug: 915907 Change-Id: I2189bfedad813e7942c7ddbd44aac78d1b895a30 Reviewed-on: https://chromium-review.googlesource.com/c/1461313 Commit-Queue: Danyao Wang <danyao@chromium.org> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#630578} -- wpt-commits: a7498ddcfeeca02e7b62ab9e9b359fcaa5764c62 wpt-pr: 15306
f1592f48542df6cd9ee7b5f8a9e58d4b7fe42bcd: Bug 1527044 [wpt PR 15133] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 12 Feb 2019 20:06:03 +0000 - rev 461341
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527044 [wpt PR 15133] - Update wpt metadata, a=testonly wpt-pr: 15133 wpt-type: metadata
e80d7b6fe06457552e2eb2d1b1751931984403a2: Bug 1527044 [wpt PR 15133] - Deflake RTCPeerConnection-track-stats.https.html., a=testonly
Henrik Boström <hbos@chromium.org> - Tue, 19 Feb 2019 11:46:39 +0000 - rev 461340
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527044 [wpt PR 15133] - Deflake RTCPeerConnection-track-stats.https.html., a=testonly Automatic update from web-platform-tests Deflake RTCPeerConnection-track-stats.https.html. This CL does the following: 1. Add a test that verifies we have a succeeded candidate pair in getStats() as soon as iceConnectionState is "connected". This is currently flaky (https://crbug.com/926170) and marked as such. 2. Add workaround to RTCPeerConnection-track-stats.https.html so that it does not flake due to 1), and mark it not flaky. 3. Move shared helper functions to RTCPeerConnection-helper.js. 4. Add test coverage for making sure we can become connected in the recvonly use case. This requires changing the prefix to ".https.html" of "RTCPeerConnection-iceConnectionState". // Already reviewed by jonasolsson@chromium.org TBR=guidou@chromium.org Bug: 922955, 926170 Change-Id: I828e46273a84447c817595a466a5e143bde30eca Reviewed-on: https://chromium-review.googlesource.com/c/1442201 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#627421} -- wpt-commits: 7179024d5dfb231073c7319948499d7e30f671cb wpt-pr: 15133
a52794d4ba349c03a5438d49293cda0bead134db: Bug 1527042 [wpt PR 15251] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 13 Feb 2019 13:08:52 +0000 - rev 461339
Push 35622 by ncsoregi@mozilla.com at Wed, 27 Feb 2019 04:32:15 +0000
Bug 1527042 [wpt PR 15251] - Update wpt metadata, a=testonly wpt-pr: 15251 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip