Bug 1452339 [wpt PR 9797] - Update payment-request IDL file, a=testonly Automatic update from web-platform-testsUpdate payment-request IDL file (#9797) wpt-commits: ab293a51c78d9a33b403385ea8f26246a44d80bf wpt-pr: 9797 wpt-commits: ab293a51c78d9a33b403385ea8f26246a44d80bf wpt-pr: 9797

Bug 1447621 [wpt PR 10122] - [css-grid] Fix testing-utils.js, a=testonly Automatic update from web-platform-tests[css-grid] Fix testing-utils.js We have been calling testGridTemplateColumnsRows() with and without arrays. Arrays are needed because the serialization of 2 tracks of the same size can be "100px 100px" or "repeat(2, 100px)". But in the rest of the cases we don't need an array, so we call the method with a single value. testGridTemplateColumnsRows() was not ready to support that, and it wasn't actually checking anything in that case. The patch modifies testing-utils.js, so it wraps values in an array when required. Now testGridTemplateColumnsRows() will be actually checking things. Change-Id: I7e360677c391df74dedb474922bf5c04247141c5 Reviewed-on: https://chromium-review.googlesource.com/973063 Reviewed-by: Sergio Villar <svillar@igalia.com> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#544681} wpt-commits: 535e9629904e3f24ac891763d5d24b8475df5926 wpt-pr: 10122 wpt-commits: 535e9629904e3f24ac891763d5d24b8475df5926 wpt-pr: 10122

Bug 1447496 [wpt PR 10116] - Attempt to fix ci_resources_unittest (#10114), a=testonly Automatic update from web-platform-testsAttempt to fix ci_resources_unittest (#10116) The test wasn't running against the downloaded Firefox Nightly but system Firefox instead, which is fixed by passing the binary path to tox (which then passes it to pytest conftest.py). The pip requirements should be managed by tox. wpt-commits: 47c9322f474fe123c6df2223bd93b8fd0056c6f9 wpt-pr: 10116 wpt-commits: 47c9322f474fe123c6df2223bd93b8fd0056c6f9 wpt-pr: 10116

Bug 1441139 [wpt PR 9672] - Test postMessage() exception order, a=testonly Automatic update from web-platform-testsTest postMessage() exception order For https://github.com/whatwg/html/pull/3508 and https://github.com/whatwg/html/pull/3557. wpt-commits: fc04bb5708878ee7b68996f8a161507022e07777 wpt-pr: 9672 wpt-commits: fc04bb5708878ee7b68996f8a161507022e07777 wpt-pr: 9672

Bug 1447543 [wpt PR 10119] - Edge doesn't do object spread yet, a=testonly Automatic update from web-platform-testsEdge doesn't do object spread yet (#10119) wpt-commits: f8920ff0580278a7d8036f534c1fd0f21fc8662d wpt-pr: 10119 wpt-commits: f8920ff0580278a7d8036f534c1fd0f21fc8662d wpt-pr: 10119

Bug 1446879 [wpt PR 10090] - user activation must survive postMessage() to call show(), a=testonly Automatic update from web-platform-testsuser activation must survive postMessage() to call show() (#10090) Check that we can call pr.show() in an iframe via postMessage(), which is triggered by user activation. wpt-commits: 92885acfbbfa2ad0fe08310857379cb4c84797c0 wpt-pr: 10090 wpt-commits: 92885acfbbfa2ad0fe08310857379cb4c84797c0 wpt-pr: 10090

Bug 1446275 [wpt PR 10068] - Update wpt metadata, a=testonly wpt-pr: 10068 wpt-type: metadata

Bug 1446275 [wpt PR 10068] - Revert "rename generic-sensor directory as sensors", a=testonly Automatic update from web-platform-testsRevert "rename generic-sensor directory as sensors" (#10068) wpt-commits: 66e0742f88e4a6a10aaf4bd887a29b1062aad9c8 wpt-pr: 10068 wpt-commits: 66e0742f88e4a6a10aaf4bd887a29b1062aad9c8 wpt-pr: 10068

Bug 1447066 [wpt PR 10098] - Exit check_stability with an error when no tests run, a=testonly Automatic update from web-platform-testsExit check_stability with an error when no tests run Similar to #10030 (which was for `wpt run`), this commit makes `wpt check-stability` return a non-zero exit code when no tests run. Also fix some code smells: * `run` was redefined by `do_delayed_imports` to a different function. Rename the other `run` method in this module to `setup_and_run`. * `retcode` was unnecessarily defined in the top scope. Remove it to avoid redefinition. * `global logger` and the call to `get_parser` were extraneous in `run` (now `setup_and_run`) and hence are removed. -- Address comments * Renaming `check_stability.run` breaks commands.json and naming conventions, so rename the other `run` in that module instead. * Only return errors for empty results when we know for sure tests are affected. wpt-commits: 7e214e852492e619254c14c351a85ac97661d847, 3a8328470d53c4501e31cec2775c4d33821c2275 wpt-pr: 10098 wpt-commits: 7e214e852492e619254c14c351a85ac97661d847, 3a8328470d53c4501e31cec2775c4d33821c2275 wpt-pr: 10098

Bug 1446543 [wpt PR 10082] - No longer allow Chrome stability check to fail, a=testonly Automatic update from web-platform-testsNo longer allow Chrome stability check to fail After #10064, Chrome jobs run successfully on Travis, so we can turn the stability check back on. Fixes #9932. wpt-commits: 4d10320c4970e1d8f3f64aac9fecde03ee0ae87e wpt-pr: 10082 wpt-commits: 4d10320c4970e1d8f3f64aac9fecde03ee0ae87e wpt-pr: 10082

Bug 1446228 [wpt PR 10063] - Update wpt metadata, a=testonly wpt-pr: 10063 wpt-type: metadata

Bug 1446228 [wpt PR 10063] - Indexed DB: Consolidate window/worker IDL tests into any.js, a=testonly Automatic update from web-platform-testsIndexed DB: Consolidate window/worker IDL tests into any.js Also, rely on HTML and DOM interfaces for dependencies rather than inline definitions for Event, EventTarget, etc. Change-Id: I58ac6515f8d2769aec6bbf1b90d9a4105639ad24 Reviewed-on: https://chromium-review.googlesource.com/965452 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#544429} wpt-commits: dacfb4465c26ab8ee6e1e618671b38905b50c02e wpt-pr: 10063 wpt-commits: dacfb4465c26ab8ee6e1e618671b38905b50c02e wpt-pr: 10063

Bug 1445765 [wpt PR 10041] - stops using wrappedJSObject in marionette executor, a=testonly Automatic update from web-platform-testsStop using wrappedJSObject in marionette executor (#10041) wpt-commits: e04e71fefa3c8d0324e5ab12b9ddcf569e134505 wpt-pr: 10041 wpt-commits: e04e71fefa3c8d0324e5ab12b9ddcf569e134505 wpt-pr: 10041

Bug 1446178 [wpt PR 10018] - Update wpt metadata, a=testonly wpt-pr: 10018 wpt-type: metadata

Bug 1446178 [wpt PR 10018] - ReadableStream: Readable byte stream must call pull if needed after receiving new chunk, a=testonly Automatic update from web-platform-testsReadableStream: Readable byte stream must call pull if needed after receiving new chunk (#10018) * Fix test that allows too much pulling * Test that byte stream pulls after enqueue wpt-commits: 6e1b5f44943705380487dc73b96b4c959487ee4d wpt-pr: 10018 wpt-commits: 6e1b5f44943705380487dc73b96b4c959487ee4d wpt-pr: 10018

Bug 1452643 [wpt PR 9843] - Update the web-share IDL file, a=testonly Automatic update from web-platform-testsUpdate the web-share IDL file (#9843) wpt-commits: 31c11a7a91486a50fceaa68f3773a5b915e8824d wpt-pr: 9843 wpt-commits: 31c11a7a91486a50fceaa68f3773a5b915e8824d wpt-pr: 9843

Bug 1447040 [wpt PR 10096] - Correctly reject in-progress body methods with AbortError, a=testonly Automatic update from web-platform-testsCorrectly reject in-progress body methods with AbortError Prior to this change, response body methods such as response.body.arrayBuffer() would reject with a TypeError if the fetch was aborted. This change makes them correctly reject with an AbortError instead. This implements stage #3 of the "Body Cancellation" section of the design doc: https://docs.google.com/document/d/1OuoCG2uiijbAwbCw9jaS7tHEO0LBO_4gMNio1ox0qlY/edit#heading=h.fvc7d7q07oio Bug: 817687 Change-Id: Ifde322d9c22485a8ba9d14fd4ffca65c4fb4745a Reviewed-on: https://chromium-review.googlesource.com/954765 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#544335} wpt-commits: f2ae7641fad03150b4238a8b34dc9bdfdf58c0dd wpt-pr: 10096 wpt-commits: f2ae7641fad03150b4238a8b34dc9bdfdf58c0dd wpt-pr: 10096

Bug 1447114 [wpt PR 10099] - Update wpt metadata, a=testonly wpt-pr: 10099 wpt-type: metadata

Bug 1447114 [wpt PR 10099] - Update serialization of drop-shadow, a=testonly Automatic update from web-platform-testsMerge pull request #10099 from csnardi/patch-9 Update serialization of drop-shadow wpt-commits: c51eaff86a080994725c948262cf2316bddd9e6c wpt-pr: 10099 wpt-commits: c51eaff86a080994725c948262cf2316bddd9e6c wpt-pr: 10099

Bug 1447176 [wpt PR 10102] - [css-typed-om] support pointer-events property, a=testonly Automatic update from web-platform-tests[css-typed-om] support pointer-events property pointer-events[1] are added to support in whitelist. there are some camelcase keywords in pointer-events. actually pre-defined keywords are interpreted ASCII case-insensitively[2]. so it was changed to accept camelcase keyword in tests. and test file are also added. [1]https://svgwg.org/svg2-draft/interact.html#PointerEventsProperty [2]https://drafts.csswg.org/css-values-4/#keywords Bug: 820299 Change-Id: Iccc0f88a69bbec68964ef55bcc5c471fea765ccf Reviewed-on: https://chromium-review.googlesource.com/968581 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: Hwanseung Lee <hwanseung@chromium.org> Cr-Commit-Position: refs/heads/master@{#544232} wpt-commits: 234faac690ec3bc8bebd39ae9b2e2b3a3b05ef82 wpt-pr: 10102 wpt-commits: 234faac690ec3bc8bebd39ae9b2e2b3a3b05ef82 wpt-pr: 10102