350bb00db2297dc7c86af8abb2a97e2f93b1cc8c: Bug 1535850 [wpt PR 15790] - Use matching sample rate for the context as for the reference file, a=testonly
Raymond Toy <rtoy@chromium.org> - Tue, 26 Mar 2019 14:09:16 +0000 - rev 467355
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535850 [wpt PR 15790] - Use matching sample rate for the context as for the reference file, a=testonly Automatic update from web-platform-tests Use matching sample rate for the context as for the reference file The reference file has a certain sample rate. Use the same for the context to reduce the amount of resampling that might be required. Regenerated the webm-decode-expected.wave file with the fixed sample rate. This also changed the SNR slightly, so update the SNR test accordingly. Also manually compared the new and old files. These differ by at most 1 LSB (16-bit). Bug: 940970 Change-Id: I979bbeb512c36d7e2eb4cba85550fa4177b8aabd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1516723 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#640341} -- wpt-commits: 1d62ca809d6c859a9ef5f48f82dac4a366c6a0eb wpt-pr: 15790
029bed7fd777db79e7268440e69e47fe7996f78e: Bug 1535933 [wpt PR 15813] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 18 Mar 2019 17:53:22 +0000 - rev 467354
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535933 [wpt PR 15813] - Update wpt metadata, a=testonly wpt-pr: 15813 wpt-type: metadata
e097f164c2a29afc57120b0edbbf1af3c41d02d8: Bug 1535933 [wpt PR 15813] - Updated the css-text test suite, a=testonly
Javier Fernandez <jfernandez@igalia.com> - Tue, 26 Mar 2019 14:09:11 +0000 - rev 467353
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535933 [wpt PR 15813] - Updated the css-text test suite, a=testonly Automatic update from web-platform-tests Updated the css-text test suite Added a few additional tests to verify some leading white-space cases with different properties. Fixed also some typos and bad design choices in some tests. Change-Id: Ic702d9ce4bd969408c4760724f1f9d4a1f6eb6fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1520829 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#640320} -- wpt-commits: 5883163db70d3401826497db01908f8a0f5138d9 wpt-pr: 15813
4e7252ab1e0e1048750b30048acb2dca82cf1fd2: Bug 1535951 [wpt PR 15726] - Update pillow to 5.4.1, a=testonly
pyup.io bot <github-bot@pyup.io> - Tue, 26 Mar 2019 14:09:08 +0000 - rev 467352
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535951 [wpt PR 15726] - Update pillow to 5.4.1, a=testonly Automatic update from web-platform-tests Update pillow from 5.2.0 to 5.4.1 (#15726) -- wpt-commits: 5df243654fcf1672d8e76d461d989651d907873a wpt-pr: 15726
3f2615ed91a1a2b92f8620b6457591bf0ee3f6b6: Bug 1503700 [wpt PR 13823] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 01 Nov 2018 15:39:06 +0000 - rev 467351
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1503700 [wpt PR 13823] - Update wpt metadata, a=testonly wpt-pr: 13823 wpt-type: metadata
309d8480b42f0c82e569ef8fbc318a35d772e212: Bug 1503700 [wpt PR 13823] - Add nested-context resource-timing tests, a=testonly
Yoav Weiss <yoav@yoav.ws> - Tue, 26 Mar 2019 14:09:02 +0000 - rev 467350
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1503700 [wpt PR 13823] - Add nested-context resource-timing tests, a=testonly Automatic update from web-platform-tests Add nested-context resource-timing tests -- wpt-commits: 75913b3b43e4cfe4676ab99c795c7c7882962b54 wpt-pr: 13823
704b5ef9b6f56ba71a4956b9f3d8f5472a80f988: Bug 1534097 [wpt PR 15700] - Update marionette_driver to 2.8.0, a=testonly
pyup.io bot <github-bot@pyup.io> - Tue, 26 Mar 2019 14:09:00 +0000 - rev 467349
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534097 [wpt PR 15700] - Update marionette_driver to 2.8.0, a=testonly Automatic update from web-platform-tests Update marionette_driver from 2.7.0 to 2.8.0 (#15700) -- wpt-commits: 6de24ef182793415932be9b2a092d94cde904b5a wpt-pr: 15700
840ba9d3e52556a45d7d6881c0bc9887ea0814b6: Bug 1535872 [wpt PR 15793] - Fix expectation in attributes-and-toJSON-method-manual.https.html, a=testonly
Danyao Wang <danyao@chromium.org> - Tue, 26 Mar 2019 14:08:58 +0000 - rev 467348
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535872 [wpt PR 15793] - Fix expectation in attributes-and-toJSON-method-manual.https.html, a=testonly Automatic update from web-platform-tests Add region to address -- Merge pull request #15793 from danyao/check-region-in-address Fix expectation in attributes-and-toJSON-method-manual.https.html -- wpt-commits: 7eac0e5f8f59273b408cc48978c3dcf02d97fd8c, fd3bdd7758a9309c32c4e7a145d98a50a9816624 wpt-pr: 15793
9eceec77aa6f1716e82333f43f398503c777aa84: Bug 1535920 [wpt PR 15810] - Screen Orientation: Add orientation-utils.js, a=testonly
Johanna <Johanna-hub@users.noreply.github.com> - Tue, 26 Mar 2019 14:08:53 +0000 - rev 467347
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535920 [wpt PR 15810] - Screen Orientation: Add orientation-utils.js, a=testonly Automatic update from web-platform-tests Screen Orientation: Add orientation-utils.js (#15810) -- wpt-commits: d46410047231acada785726516a150543725338c wpt-pr: 15810
788f7d38f4e546790a023cdbbc107891b6445206: Bug 1535914 [wpt PR 15808] - Install packages we need on Travis, a=testonly
Sam Sneddon <me@gsnedders.com> - Tue, 26 Mar 2019 14:08:51 +0000 - rev 467346
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535914 [wpt PR 15808] - Install packages we need on Travis, a=testonly Automatic update from web-platform-tests Make sure we install extra dependencies for all CI jobs that run browsers. -- Fix #15728: install pulseaudio as Firefox requires it -- wpt-commits: 005b09f8699dae8ab7719e948390b3cc2697d075, c8bb42df48ba9d6c275ba1a6ff67ea1e6f3d9a72 wpt-pr: 15808
e913f57ffde8a35315f7881c2b4cb5aa9cab7f63: Bug 1533756 [wpt PR 15672] - Remove Chrome's unified plan flag (now on by default), a=testonly
Philip Jägenstedt <philip@foolip.org> - Tue, 26 Mar 2019 14:08:49 +0000 - rev 467345
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1533756 [wpt PR 15672] - Remove Chrome's unified plan flag (now on by default), a=testonly Automatic update from web-platform-tests Remove Chrome's unified plan flag (now on by default) (#15672) -- wpt-commits: d776d049fc35ab1bb6faf183acd69858ddf92cc3 wpt-pr: 15672
7b93496f93b72f36a140785a122ba98022d26ddc: Bug 1535834 [wpt PR 15787] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 18 Mar 2019 17:38:15 +0000 - rev 467344
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535834 [wpt PR 15787] - Update wpt metadata, a=testonly wpt-pr: 15787 wpt-type: metadata
48205c73bdca868dc372517f2d657dd2514a93b3: Bug 1535834 [wpt PR 15787] - [css-properties-values-api] Substitute initial values as computed values., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Tue, 26 Mar 2019 14:08:44 +0000 - rev 467343
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535834 [wpt PR 15787] - [css-properties-values-api] Substitute initial values as computed values., a=testonly Automatic update from web-platform-tests [css-properties-values-api] Substitute initial values as computed values. Registered custom properties substitute as token sequences equivalent to their computed values. We already do this correctly for non-initial values, but when substituting the initial value of a registered custom property, we would substitute the original token sequence instead of the computed value equivalent. R=futhark@chromium.org Bug: 641877 Change-Id: Icc9b8844d98cefd030be0daa91aef7963d55d7bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1517700 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#640268} -- wpt-commits: 73bbfeb42a30db594a44256b76966cb0f35b1a04 wpt-pr: 15787
e50ce15bbe5613efdaec4616be02b5c795faff37: Bug 1535841 [wpt PR 15788] - HTML: window.document and discarded browsing contexts, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 26 Mar 2019 14:08:41 +0000 - rev 467342
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535841 [wpt PR 15788] - HTML: window.document and discarded browsing contexts, a=testonly Automatic update from web-platform-tests HTML: window.document and discarded browsing contexts -- wpt-commits: 1c31e4269849395cb87738add3efd6f14866d86d wpt-pr: 15788
94c16b51d515e3fb32be07bf02d8832d97161b26: Bug 1534200 [wpt PR 15720] - HTML: test WindowProxy self references, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 26 Mar 2019 14:08:39 +0000 - rev 467341
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1534200 [wpt PR 15720] - HTML: test WindowProxy self references, a=testonly Automatic update from web-platform-tests HTML: test WindowProxy self references For https://github.com/whatwg/html/pull/4410. -- wpt-commits: 1a896b5997ef877e8f6e3005176857f615d58cd3 wpt-pr: 15720
18c0f69769759253d3a70a5e6ef7f98570b300cf: Bug 1535887 [wpt PR 15796] - Revert "Make pointer capture work in same origin frame", a=testonly
Findit <findit-for-me@appspot.gserviceaccount.com> - Tue, 26 Mar 2019 14:08:37 +0000 - rev 467340
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535887 [wpt PR 15796] - Revert "Make pointer capture work in same origin frame", a=testonly Automatic update from web-platform-tests Revert "Make pointer capture work in same origin frame" This reverts commit d44248f2a896421c1382c1dbbf0d7e1a9b798470. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 640055 as the culprit for flakes in the build cycles as shown on: https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZDQ0MjQ4ZjJhODk2NDIxYzEzODJjMWRiYmYwZDdlMWE5Yjc5ODQ3MAw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests%20%28dbg%29%281%29/78896 Sample Failed Step: webkit_layout_tests Sample Flaky Test: virtual/user-activation-v2/fast/events/pointerevents/mouse-pointer-capture-in-iframe.html Original change's description: > Make pointer capture work in same origin frame > > We used to send mouse event to the subframe before apply the pointer > capture target, and it causes the pointer capture doesn't work when > capture to a outer frame target and move to inner frame. > > This CL changes three things: > 1. 'Rename' the |capturing_mouse_events_element_| to > |capturing_subframe_element_| as it only used for the frame capture > (There is plan to remove the frame capture logic once we have pointer > capture work correctly) > 2. On HandleMouse*Event, instead of always perform a hit test, we use > either frame capture target or pointer capture target to re-construct > the HitTestResult. > 3. When using the capture target, update the hover active state for > capture target. > > This change makes captured pointer event sent correctly when over > same origin frame, and also decrease the hit_test_count because of > frame capturing. > > Note that after this change, we still NOT allow set/release pointer > capture across same-origin frame as the pointer id and active statue > is per frame. > > See design doc: > https://docs.google.com/document/d/1cOZu98UuKk5bdARUQKmj2Q8YoEMpd9l78T0k-cf5ttc/ > > This change is under a blink flag UnifiedPointerCaptureInBlink. > > Change-Id: I61c6a02086535d2a145df9d414df0bdc9673101e > Bug: 936190, 919908 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1446556 > Commit-Queue: Ella Ge <eirage@chromium.org> > Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> > Reviewed-by: David Bokan <bokan@chromium.org> > Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> > Cr-Commit-Position: refs/heads/master@{#640055} Change-Id: Idf2d9cd99b54ad4caa1517c54ba9c65401014ffa No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 936190, 919908 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1519468 Cr-Commit-Position: refs/heads/master@{#640160} -- wpt-commits: ea3cae9746c39e8192b91181044144c60d9388e8 wpt-pr: 15796
03008a8e6f92e873b253a8404bd8bc7171a3a4eb: Bug 1535636 [wpt PR 15776] - Update sleep.py to use high resolution timer, a=testonly
Erik Anderson <Erik.Anderson@microsoft.com> - Tue, 26 Mar 2019 14:08:35 +0000 - rev 467339
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535636 [wpt PR 15776] - Update sleep.py to use high resolution timer, a=testonly Automatic update from web-platform-tests Update sleep.py to use high resolution timer In a previous change to this file (https://chromium-review.googlesource.com/c/chromium/src/+/1469655), I added a check after the sleep completes to check if we slept long enough. After submitting this to Microsoft's test environment which runs on Hyper-V VMs, we found that the test was still flaky because the timer we're using in the Python web server doesn't have sufficient precision. In the previous change, I had considered using time.clock() which uses QPC on Windows. However, on Unix, it maps to CPU time which means it doesn't advance while we're switched out for the sleep. This change uses time.default_timer() which is the best of both worlds: with Python 2 it maps to time.clock() on Windows and to time.time() on non-Windows platforms while on Python 3.3+ it maps to time.perf_counter(); this ensures it is measuring wall time with the most accurate clock available for the platform. This change has been run for over two weeks in Microsoft's test environment without any issues. Change-Id: I30fc5f72de24fafe0766ca9b607b63290e47fae5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1516914 Reviewed-by: Robert Ma <robertma@chromium.org> Commit-Queue: Robert Ma <robertma@chromium.org> Cr-Commit-Position: refs/heads/master@{#640122} -- wpt-commits: 7d3ab930ab623a4bcbb2af6e5d87ad8a851bbee0 wpt-pr: 15776
3acc1b6ee08e5dea97d00cbb97ce1d293385551c: Bug 1535512 [wpt PR 15765] - Send screenshots from Azure to wpt.fyi, a=testonly
Robert Ma <robertma@chromium.org> - Tue, 26 Mar 2019 14:08:32 +0000 - rev 467338
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535512 [wpt PR 15765] - Send screenshots from Azure to wpt.fyi, a=testonly Automatic update from web-platform-tests Store reftest screenshots on Azure as wpt_screenshot{_*}.txt in the build artifact zip. -- wpt-commits: 167e3ee6dfff8e94d6d078a4c21897575d27e53a wpt-pr: 15765
2b6f39d7a66eab5cdb5ed50b064fb455c53870f0: Bug 1535876 [wpt PR 15795] - Remove redundant test in show-method-postmessage-manual.https.html, a=testonly
Danyao Wang <danyao@chromium.org> - Tue, 26 Mar 2019 14:08:30 +0000 - rev 467337
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535876 [wpt PR 15795] - Remove redundant test in show-method-postmessage-manual.https.html, a=testonly Automatic update from web-platform-tests Remove redundant test -- Merge pull request #15795 from danyao/danyao/remove-redundant-test Remove redundant test in show-method-postmessage-manual.https.html -- wpt-commits: 607ee74326a5c8eea4460c05dffc328675760817, 8d8d9c28bbdc60134ed116123ce9fce6062a63eb wpt-pr: 15795
ad1c36b163745d31558926a65b5a1a3e4031f0d2: Bug 1535613 [wpt PR 15775] - [ResourceTiming] Rename test resource_memory_cached->resource_reuse, a=testonly
Nicolás Peña Moreno <npm@chromium.org> - Tue, 26 Mar 2019 14:08:27 +0000 - rev 467336
Push 35796 by csabou@mozilla.com at Mon, 01 Apr 2019 21:56:51 +0000
Bug 1535613 [wpt PR 15775] - [ResourceTiming] Rename test resource_memory_cached->resource_reuse, a=testonly Automatic update from web-platform-tests [ResourceTiming] Rename test resource_memory_cached->resource_reuse The test does not seem to exercise the memory cache, so I propose renaming the test to something that is more implementation-independent. Also, use an img_src variable to avoid repeating the location in the script. Change-Id: I88e4574d5267a75586fc7b74f39f67e0aab2bc04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1516789 Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#640106} -- wpt-commits: c7a85cb312e815f887fb851b7d1951348b54de8c wpt-pr: 15775
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip