74ac4fe9e8cf9082e60a53ab1fcd3d5cceb552d9: Bug 1499975 [wpt PR 13590] - fix: show requires user activation, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Thu, 01 Nov 2018 11:19:57 +0000 - rev 501399
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499975 [wpt PR 13590] - fix: show requires user activation, a=testonly Automatic update from web-platform-testsfix: show requires user activation (#13590) -- wpt-commits: be86392ec8f14a6f3299bb5ac9fd633cfbb2edb8 wpt-pr: 13590
248da4784ede5963d141360f056783bd6101b72a: Bug 1500261 [wpt PR 13604] - Use content width to calculate percentage text-indent, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 01 Nov 2018 10:56:08 +0000 - rev 501398
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1500261 [wpt PR 13604] - Use content width to calculate percentage text-indent, a=testonly Automatic update from web-platform-testsUse content width to calculate percentage text-indent The new line in TestExpectations is for an old WPT test that checks for the old behavior. BUG=884588 R=eae@chromium.org Change-Id: I560e8d240d773536d084b598ac76261f9ecef81a Reviewed-on: https://chromium-review.googlesource.com/c/1285109 Commit-Queue: Stefan Zager <szager@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#600989} -- wpt-commits: 824f0c1df556305042b8aa8073c32e9ef86c3efa wpt-pr: 13604
d5bd46b7279ec26642e9611cc93c9a367e800f5a: Bug 1500204 [wpt PR 13601] - Update requests to 2.20.0, a=testonly
pyup.io bot <github-bot@pyup.io> - Mon, 29 Oct 2018 17:18:02 +0000 - rev 501397
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1500204 [wpt PR 13601] - Update requests to 2.20.0, a=testonly Automatic update from web-platform-testsUpdate requests to 2.20.0 (#13601) -- wpt-commits: 4d43b10637109e425e44641ea1d6a1db59405c07 wpt-pr: 13601
bd0a5d240b3973ade396a424f7736022a07159fc: Bug 1499505 [wpt PR 13549] - [Background Fetch] Throw DOMException for responseReady on abort., a=testonly
Rayan Kanso <rayankans@chromium.org> - Mon, 29 Oct 2018 17:17:53 +0000 - rev 501396
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499505 [wpt PR 13549] - [Background Fetch] Throw DOMException for responseReady on abort., a=testonly Automatic update from web-platform-tests[Background Fetch] Throw DOMException for responseReady on abort. According to the spec, responseReady in BackgroundFetchRecord should throw an AbortError DOMException if the fetch was abandoned. https://wicg.github.io/background-fetch/#create-record-objects (2.4.3) Change-Id: Ieadf278acd061e05b8822014d0934f050fcac702 Reviewed-on: https://chromium-review.googlesource.com/c/1283692 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#600769} -- wpt-commits: f3ca7fcb4507476c55812417b8d451c9ef33a380 wpt-pr: 13549
d1698a026e53f3ae2481ec932c792c8b2b28e297: Bug 1500421 [wpt PR 13528] - [Background Fetch] Simplify fetch storage workflow., a=testonly
Rayan Kanso <rayankans@chromium.org> - Mon, 29 Oct 2018 17:17:51 +0000 - rev 501395
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1500421 [wpt PR 13528] - [Background Fetch] Simplify fetch storage workflow., a=testonly Automatic update from web-platform-tests[Background Fetch] Simplify fetch storage workflow. In addition, MatchAll should return all records, including unprocessed ones. To support this, the following changes were made: - Creating a registration also stores all the requests with an empty response in the cache. - When an individual request is processed, the failure reason (if any) is stored in the metadata. - The logic of GetSettledFetchesTask was moved to MarkRegistrationForDeletionTask. It checks the metadata rather than the cache itself to find a failure reason (if any). - Match/MatchAll logic was moved to a new database task (MatchRequestsTask). A new API call was added to the cache storage to allow querying request/response pairs. If a response is found to be empty it will be exposed as a nullptr. Change-Id: I631a3ef3da95117aed759a675fe591da5201eeca Reviewed-on: https://chromium-review.googlesource.com/c/1280851 Reviewed-by: Peter Beverloo <peter@chromium.org> Reviewed-by: Steven Holte <holte@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Reviewed-by: Ben Kelly <wanderview@chromium.org> Reviewed-by: Mugdha Lakhani <nator@chromium.org> Commit-Queue: Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#600768} -- wpt-commits: b38f09e16029e5944ef273644ba52588977515b7 wpt-pr: 13528
d5395ccafc3225bcc3e108ee602ce166cbf9c1dd: Bug 1499892 [wpt PR 13584] - [css-regions] Inheritance and initial values, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Mon, 29 Oct 2018 17:17:49 +0000 - rev 501394
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499892 [wpt PR 13584] - [css-regions] Inheritance and initial values, a=testonly Automatic update from web-platform-tests[css-regions] Inheritance and initial values (#13584) Test that properties do not inherit. Test that properties have initial values according to spec. https://drafts.csswg.org/css-regions/#property-index -- wpt-commits: 8ca1dc455a45eb6d8429ddf63ad423f6619c5674 wpt-pr: 13584
877caab79b9b39e86e52b7caa4e06ce351c2ef9c: Bug 1499767 [wpt PR 13574] - [css-scroll-anchoring] Inheritance, initial value, a=testonly
Eric Willigers <ericwilligers@chromium.org> - Mon, 29 Oct 2018 17:17:47 +0000 - rev 501393
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499767 [wpt PR 13574] - [css-scroll-anchoring] Inheritance, initial value, a=testonly Automatic update from web-platform-tests[css-scroll-anchoring] Inheritance, initial value Test that property inherits according to spec. Test that property has initial value according to spec. https://drafts.csswg.org/css-scroll-anchoring/#property-index -- Merge pull request #13574 from ewilligers/scroll-anchoring-inheritance [css-scroll-anchoring] Inheritance, initial value -- wpt-commits: 1772ed703f2135623e5443bb3a07b1d0110f7076, ca59071370a1e596a021ddea991de64cc374a545 wpt-pr: 13574
8af7bfedab592adf05c0b575d9fa69ccf3517260: Bug 1498683 [wpt PR 13483] - Add a test for the WebAssembly Web API., a=testonly
Ms2ger <Ms2ger@gmail.com> - Mon, 29 Oct 2018 17:17:45 +0000 - rev 501392
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1498683 [wpt PR 13483] - Add a test for the WebAssembly Web API., a=testonly Automatic update from web-platform-testsAdd a test for the WebAssembly Web API. (#13483) -- wpt-commits: 042665de556151e01cb2db79896552dbfafe3d58 wpt-pr: 13483
2bdb27b211a5a46c78149ecf70df97f8aaf39422: Bug 1499133 [wpt PR 13527] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 15 Oct 2018 21:36:44 +0000 - rev 501391
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499133 [wpt PR 13527] - Update wpt metadata, a=testonly wpt-pr: 13527 wpt-type: metadata
d1bc4a5b5063f1a0771ab6c115d254dd46c78bf6: Bug 1499133 [wpt PR 13527] - [css-properties-values-api] Support calc() values for <integer>., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 29 Oct 2018 17:17:39 +0000 - rev 501390
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499133 [wpt PR 13527] - [css-properties-values-api] Support calc() values for <integer>., a=testonly Automatic update from web-platform-tests[css-properties-values-api] Support calc() values for <integer>. For custom properties registered with <integer>, it should according to CSS Values and Units Level 4 be possible to apply non-integral values, and then have the value round to the nearest integer computed value time. To do this, this CL ...: * Changes the parsing of <integer> values such that non-integral calc() expressions are allowed. * Recognizes such calc()-expressions computed-value time, resolves them, and rounds them to the nearest integer. * Wraps values such as CSS.number(1.5) in calc() if necessary, when setting such values using Typed OM. R=futhark@chromium.org Bug: 641877 Change-Id: I2d4d7c4d72c9b2069f2fe10b1be1b4b94d5900e2 Reviewed-on: https://chromium-review.googlesource.com/c/1280663 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#600716} -- wpt-commits: 979839c026d9a272a0c5c09097b92b74b00ff90e wpt-pr: 13527
83e85e319dabe19085a1a1039e8c3ff4040d0d2b: Bug 1499853 [wpt PR 13580] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 18 Oct 2018 01:28:47 +0000 - rev 501389
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499853 [wpt PR 13580] - Update wpt metadata, a=testonly wpt-pr: 13580 wpt-type: metadata
45bb8c168f4e84508bc2214a915d5093a0a7bcff: Bug 1499853 [wpt PR 13580] - Update data URL test case for empty MIME parameter, a=testonly
Domenic Denicola <d@domenic.me> - Mon, 29 Oct 2018 17:17:34 +0000 - rev 501388
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499853 [wpt PR 13580] - Update data URL test case for empty MIME parameter, a=testonly Automatic update from web-platform-testsUpdate data URL test case for empty MIME parameter This was missed in #12925. -- wpt-commits: 8de8728b667ec03234fc61653cb4f58ac50bfcc5 wpt-pr: 13580
e6f3145bd6c66e937b66d87977d942f4e60c7d2f: Bug 1499878 [wpt PR 13582] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 18 Oct 2018 02:23:43 +0000 - rev 501387
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499878 [wpt PR 13582] - Update wpt metadata, a=testonly wpt-pr: 13582 wpt-type: metadata
ca02427a563904a6eb000672cf8c626b2c19c07b: Bug 1499878 [wpt PR 13582] - [css-properties-values-api] Test styleMap in paint worklet., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 29 Oct 2018 17:17:29 +0000 - rev 501386
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499878 [wpt PR 13582] - [css-properties-values-api] Test styleMap in paint worklet., a=testonly Automatic update from web-platform-tests[css-properties-values-api] Test styleMap in paint worklet. Unfortunately, the existing test for this does too much behind a single green square. If even a single assertion were to fail, it would hide the result of all the other rests. At the same time, adding 40something tests is perhaps a bit excessive, so I've tried to reduce that number somewhat (mostly by only testing one of the initial value cases, which I think is reasonable). The aspect of the deleted test which verified that values were observable from all API entry points (has, get, getAll, size and iterator) is now a separate test as well. R=ikilpatrick@chromium.org Bug: 641877 Change-Id: Ie9316583ccef0ee4ddcaf688b7c1fac422649a39 Reviewed-on: https://chromium-review.googlesource.com/c/1286855 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#600699} -- wpt-commits: b0d6f94eff4e76277e4afa70c2b098fdd0e99e19 wpt-pr: 13582
0483c2e4f01182603af779075bc33ce09aa506b6: Bug 1499879 [wpt PR 13583] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 18 Oct 2018 02:32:58 +0000 - rev 501385
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499879 [wpt PR 13583] - Update wpt metadata, a=testonly wpt-pr: 13583 wpt-type: metadata
692c8df1841c1398dc83fe1c3e30f440e9154869: Bug 1499879 [wpt PR 13583] - [css-properties-values-api] Test that interpolated values reach worklet., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 29 Oct 2018 17:17:23 +0000 - rev 501384
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1499879 [wpt PR 13583] - [css-properties-values-api] Test that interpolated values reach worklet., a=testonly Automatic update from web-platform-tests[css-properties-values-api] Test that interpolated values reach worklet. R=ikilpatrick@chromium.org Bug: 641877 Change-Id: Ic0403289f9deaf97369962d6901bafb58dc46931 Reviewed-on: https://chromium-review.googlesource.com/c/1283018 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#600698} -- wpt-commits: 4b1465879f1439b31dc7627b3f5bb285775ccaa3 wpt-pr: 13583
2980304187d7d6e0355537d660f95e70e7c60202: Bug 1493416 [wpt PR 13165] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 19 Oct 2018 14:21:50 +0000 - rev 501383
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1493416 [wpt PR 13165] - Update wpt metadata, a=testonly wpt-pr: 13165 wpt-type: metadata
de13d03cc138d17a28e154146830caaff4c5b7d1: Bug 1493416 [wpt PR 13165] - [service-workers] Refactor to use async cleanup, a=testonly
jugglinmike <mike@mikepennisi.com> - Mon, 29 Oct 2018 17:17:18 +0000 - rev 501382
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1493416 [wpt PR 13165] - [service-workers] Refactor to use async cleanup, a=testonly Automatic update from web-platform-tests[service-workers] Refactor to use async cleanup (#13165) [service-workers] Refactor to use async cleanup Previously, many tests un-registered service workers only after all assertions had been satisfied. This meant that failing tests would *not* un-register workers. In order to account for workers that persisted from previous test failures, the tests included "setup" code to defensively un-register such workers. The `Test#add_cleanup` method was recently extended to support asynchronous "clean up" operations [1], but the functionality is only available to tests declared using `promise_test`. Update tests which were previously declared with `async_test` and use the new "async cleanup" API to schedule service worker un-registration so that it occurs regardless of the result of each test. [1] https://github.com/web-platform-tests/wpt/pull/8748 -- wpt-commits: 1569ae03d34aa2d1eb2fce5de52eba07673eae2b wpt-pr: 13165
b5e8720c9f201c0f78ca55b5112aef1ac32f78cf: Bug 1498991 [wpt PR 13514] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 15 Oct 2018 08:55:10 +0000 - rev 501381
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1498991 [wpt PR 13514] - Update wpt metadata, a=testonly wpt-pr: 13514 wpt-type: metadata
7b4a82998fe9bb102ea6b35125bec325778dc455: Bug 1498991 [wpt PR 13514] - Revise inline item and block-level replaced element handling Element#innerText, a=testonly
Yoshifumi Inoue <yosin@chromium.org> - Mon, 29 Oct 2018 17:17:13 +0000 - rev 501380
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1498991 [wpt PR 13514] - Revise inline item and block-level replaced element handling Element#innerText, a=testonly Automatic update from web-platform-testsRevise inline item and block-level replaced element handling Element#innerText This patch changes inline item and block-level replaced handling in Element#innerText for improving interrop with adding test cases to WPT test file. Examples: * abc <img> def => "abc def"; not collapse spaces around <img> * <canvas></canvas> abc => " abc"; not collapse space after <canvas> * abc <img style="display:block"> def => "abc\ndef"; recognize block with style This patch also updates of layout test expectations since existing expectations were produced by Element#innerText with bug fixed by this patch. Bug: 894701 Cq-Include-Trybots: luci.chromium.try‚Äč:linux_layout_tests_layout_ng Change-Id: I72d7eec3436d0cfa0226b5efa3adbc4c990f06c5 Reviewed-on: https://chromium-review.googlesource.com/c/1277802 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by: Yoichi Osato <yoichio@chromium.org> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#600671} -- wpt-commits: f68ddc5d4e458d7855cbb4cb9cd5597c03e7e425 wpt-pr: 13514
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip