ed47c026dce2aea919483f2adbba6f8c274de585: Bug 1470658 [wpt PR 11636] - [css-color] Parsing color and opacity, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Sat, 07 Jul 2018 00:07:36 +0000 - rev 426133
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1470658 [wpt PR 11636] - [css-color] Parsing color and opacity, a=testonly Automatic update from web-platform-testsMerge pull request #11636 from ewilligers/css-color-parsing [css-color] Parsing color and opacity -- wpt-commits: 8bb14e8b2bd36d97b216ef72ec46eaae44695707 wpt-pr: 11636
d5982da03e7f918014b9ba84660c88e0243b6cee: Bug 1468782 [wpt PR 11508] - Update requests to 2.19.1, a=testonly
pyup-bot <github-bot@pyup.io> - Sat, 07 Jul 2018 00:06:19 +0000 - rev 426132
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1468782 [wpt PR 11508] - Update requests to 2.19.1, a=testonly Automatic update from web-platform-testsUpdate requests from 2.18.4 to 2.19.1 -- Update requests from 2.18.4 to 2.19.1 -- wpt-commits: 1b5a507e1d141b6c8cdf14897ff206e85fff0753, c88d124cd2bcd2760735fac91a3e2eef4693ad05 wpt-pr: 11508
69c13f6a5171a209ba5ad16ae551a38f5b5a1d50: Bug 1472270 [wpt PR 11733] - [fullscreen] Do not return value from cleanup fns, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Sat, 07 Jul 2018 00:05:00 +0000 - rev 426131
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472270 [wpt PR 11733] - [fullscreen] Do not return value from cleanup fns, a=testonly Automatic update from web-platform-tests[fullscreen] Do not return value from cleanup fns Today, the return value of functions provided to the global `add_cleanup` function has no effect on the behavior of the test runner. An upcoming feature addition to testharness.js will cause the return value to influence test results [1]. Despite this, some existing tests have already been authored to return a value: the result of `document.exitFullScreen`. Although this is expected to be a Promise in conforming implementations, some browsers do not yet implement this functionality. To allow the new test harness feature to land without introducing harness errors, refactor existing tests to omit a return value. Additionally, use `Promise.prototype.catch` to avoid race conditions resulting from unhandled Promise rejections (which trigger a harness error in testharness.js today). [1] https://github.com/web-platform-tests/wpt/issues/6075 -- wpt-commits: 31a51c70f74e23dc52f2033e552990a03f3166a9 wpt-pr: 11733
5c89001100bf5a44fa6a8e42c5f25d8946ce930a: Bug 1472379 [wpt PR 11740] - [html] Do not return value from cleanup fns, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Sat, 07 Jul 2018 00:03:42 +0000 - rev 426130
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472379 [wpt PR 11740] - [html] Do not return value from cleanup fns, a=testonly Automatic update from web-platform-tests[html] Do not return value from cleanup fns Today, the return value of functions provided to the `Test#add_cleanup` function has no effect on the behavior of the test runner. Despite this, some existing tests have already been authored to return a value: the result of `Element#removeChild`. An upcoming feature addition to testharness.js will cause the return value to influence test results [1]. To allow the new test harness feature to land without introducing harness errors, refactor existing tests to omit a return value. [1] https://github.com/web-platform-tests/wpt/issues/6075 -- wpt-commits: 21369c1a88085d4804d520887978392d19c8c656 wpt-pr: 11740
99f8104e102031f0c9e931f1dc02abd6e286d39a: Bug 1472392 [wpt PR 11741] - [fetch] Do not return value from cleanup fns, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Sat, 07 Jul 2018 00:02:25 +0000 - rev 426129
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472392 [wpt PR 11741] - [fetch] Do not return value from cleanup fns, a=testonly Automatic update from web-platform-tests[fetch] Do not return value from cleanup fns Today, the return value of functions provided to the `Test#add_cleanup` function has no effect on the behavior of the test runner. Despite this, some existing tests have already been authored to return the `null` value. An upcoming feature addition to testharness.js will cause the return value to influence test results [1]. To allow the new test harness feature to land without introducing harness errors, refactor existing tests to omit a return value. [1] https://github.com/web-platform-tests/wpt/issues/6075 -- wpt-commits: 86455a624bb05eb7503ccbe340dca973f5dea4c8 wpt-pr: 11741
613c6059f12d89a8ec27ea4d8af9bf66d6ea0f8a: Bug 1471870 [wpt PR 11706] - Fix Python 3 errors for wpt lint/serve, a=testonly
Kagami Sascha Rosylight <saschanaz@outlook.com> - Sat, 07 Jul 2018 00:01:07 +0000 - rev 426128
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1471870 [wpt PR 11706] - Fix Python 3 errors for wpt lint/serve, a=testonly Automatic update from web-platform-testsFix Python 3 errors for wpt lint/serve (#11706) -- wpt-commits: 27406c9d238ac80c43bb62e87cd0305f59294527 wpt-pr: 11706
b67baf529a3e9476ec382e4cf5c61eb330014b48: Bug 1472144 [wpt PR 11728] - [css-cascade] parsing tests for 'all' property, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Fri, 06 Jul 2018 23:59:49 +0000 - rev 426127
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472144 [wpt PR 11728] - [css-cascade] parsing tests for 'all' property, a=testonly Automatic update from web-platform-testsMerge pull request #11728 from ewilligers/css-cascade-parsing [css-cascade] parsing tests for 'all' property -- wpt-commits: 1bcca71fe881bcb60c73abde25c808e89e7af2fd wpt-pr: 11728
c754d5346141dc745b63b89576aeeb1a0f54cda1: Bug 1471808 [wpt PR 11702] - [css-text] Update break-spaces text to white-space property, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Fri, 06 Jul 2018 23:58:29 +0000 - rev 426126
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1471808 [wpt PR 11702] - [css-text] Update break-spaces text to white-space property, a=testonly Automatic update from web-platform-testsMerge pull request #11702 from frivoal/css-text-2465 [css-text] Update break-spaces text to white-space property -- wpt-commits: 6e186ec11aad73c04bdf13cdecfd85b3b62e0fcc wpt-pr: 11702
88745ede32dd2974ef76b0ae26f89f887f4bec1f: Bug 1472407 [wpt PR 11743] - fix(resources/testdriver): correct syntax, a=testonly
Kagami Sascha Rosylight <saschanaz@outlook.com> - Fri, 06 Jul 2018 23:57:04 +0000 - rev 426125
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472407 [wpt PR 11743] - fix(resources/testdriver): correct syntax, a=testonly Automatic update from web-platform-testsfix(resources/testdriver): correct syntax (#11743) -- wpt-commits: e2dcb12445c1e7dd01cf90a7a8302492cc3f3b59 wpt-pr: 11743
cb257b6be6c5059e8f0864561d2d6ee46c2f18a6: Bug 1472106 [wpt PR 11724] - Async Cookies: Update Cookie Store API to match spec., a=testonly
Victor Costan <pwnall@chromium.org> - Fri, 06 Jul 2018 23:55:46 +0000 - rev 426124
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472106 [wpt PR 11724] - Async Cookies: Update Cookie Store API to match spec., a=testonly Automatic update from web-platform-testsAsync Cookies: Update Cookie Store API to match spec. This CL changes the signatures of cookieStore.{get,getAll,set,delete} and introduces the CookieStoreDeleteOptions and CookieStoreSetExtraOptions dictionary. The CL also updates the CookieListItem dictionary. TBR=haraken Bug: 729800 Change-Id: Iaa62b5a51cc79b19cb567be30a2f0dda54e326d8 Reviewed-on: https://chromium-review.googlesource.com/1117868 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#571736} -- wpt-commits: 0e96b1f8627cf798ebea0c2a0cdf6b5d8cb8825e wpt-pr: 11724
82e492bb2e6b9e25bff86950fe3ae1e699bc577f: Bug 1472377 [wpt PR 11739] - Remove duplicate test keyboard-map-two-parallel-requests.https.html, a=testonly
Mrunal Kapade <mrunal.kapade@intel.com> - Fri, 06 Jul 2018 23:54:28 +0000 - rev 426123
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472377 [wpt PR 11739] - Remove duplicate test keyboard-map-two-parallel-requests.https.html, a=testonly Automatic update from web-platform-testsRemove duplicate test keyboard-map-two-parallel-requests.https.html navigator-keyboard-map-two-parallel-requests.https.html also does same thing. BUG= Change-Id: If5acfe46aada93528f8821030996a9745bc19168 Reviewed-on: https://chromium-review.googlesource.com/1121346 Reviewed-by: Gary Kacmarcik <garykac@chromium.org> Commit-Queue: Mrunal Kapade <mrunal.kapade@intel.com> Cr-Commit-Position: refs/heads/master@{#571723} -- wpt-commits: a2027fd6e9201443b5a86ad137cbb42869976ddc wpt-pr: 11739
c689c172235834971e3a07f40fab8ade2a9e9fee: Bug 1470626 [wpt PR 11634] - [Squad] Generate ::before/::after/::backdrop in style recalc., a=testonly
Rune Lillesveen <futhark@chromium.org> - Fri, 06 Jul 2018 23:53:11 +0000 - rev 426122
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1470626 [wpt PR 11634] - [Squad] Generate ::before/::after/::backdrop in style recalc., a=testonly Automatic update from web-platform-tests[Squad] Generate ::before/::after/::backdrop in style recalc. We used to create these pseudo elements and their computed styles in Element::AttachLayoutTree when building the layout tree. Now we create or dispose these elements from style recalc, that is, UpdatePseudoElement. To make pseudo elements live through a style recalc with a layout tree re-attach we no longer clear the pseudo elements during DetachLayoutTree for performing_reattach=true. We do however need to clear the pseudo elements which do not get a layout object for the re-attach. That is done in AttachLayoutTree for the originating element when the originating element does not generate a layout box. We stop using the pseudo style cache on ComputedStyle for PseudoElements and instead return the ComputedStyle when creating the pseudo element and store it as non-attached style which can later be retrieved when attaching the layout object. An effect of this change is that we can detect transitions on pseudo elements when ancestors display types changes and causes re-attachment. That is issue 836140. ::first-letter may still be generated during layout tree building, and the ::first-letter layout structure may still be updated during style recalc. Bug: 836126, 836140 Change-Id: Iafad705b7a7b988d4c1598e8a126ce0d79c5873d Reviewed-on: https://chromium-review.googlesource.com/1112244 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571665} -- wpt-commits: ec35b03ca5e8eec6eb1767a77f0aea13855515a3 wpt-pr: 11634
5fec2e1e5e67d6ec5d2ca5b62b4daf7dfa18005f: Bug 1471607 [wpt PR 11688] - [LayoutNG] Allow epsilon when fitting into a line, a=testonly
Koji Ishii <kojii@chromium.org> - Fri, 06 Jul 2018 23:51:53 +0000 - rev 426121
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1471607 [wpt PR 11688] - [LayoutNG] Allow epsilon when fitting into a line, a=testonly Automatic update from web-platform-tests[LayoutNG] Allow epsilon when fitting into a line When NGLineBreaker tries to fit items into a line, rounding errors are hard to avoid. One case is to fit `monospace` font into a container whose `width` is set by `ch` unit. Blink computes `ch` units in float, then round to LayoutUnit. This rounding often prevents the specified number of characters to fit into the line. All 4 impls pass this test for `3ch` to `100ch`. Bug: 636993 Cq-Include-Trybots: luci.chromium.try :linux_layout_tests_layout_ng Change-Id: I9fe68a8bb44820aa15c7eb8c564776688c8320ee Reviewed-on: https://chromium-review.googlesource.com/1116409 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#571642} -- wpt-commits: c360ca023dc5c341065de0f2814914b3c6004e4f wpt-pr: 11688 MozReview-Commit-ID: IgzIRG31IMn
d7b449aa4ab116490c6be9048b43fa94d16b055e: Bug 1468880 [wpt PR 11511] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 16 Jun 2018 02:21:31 +0000 - rev 426120
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1468880 [wpt PR 11511] - Update wpt metadata, a=testonly wpt-pr: 11511 wpt-type: metadata
e0c78da2588035394f8d24faa4150b04af21c13e: Bug 1468880 [wpt PR 11511] - [testdriver.js] Implement `bless` method, a=testonly
jugglinmike <mike@mikepennisi.com> - Fri, 06 Jul 2018 23:50:28 +0000 - rev 426119
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1468880 [wpt PR 11511] - [testdriver.js] Implement `bless` method, a=testonly Automatic update from web-platform-tests[testdriver.js] Implement `bless` method (#11511) A common use case for the testdriver.js library is to create a task that was triggered by user interaction [1]. Doing so using the current API requires a fair amount of logic which is unrelated to the behavior under test. This has a number of drawbacks: - it makes tests less descriptive - it makes tests less uniform both in terms of implementation and in terms of user experience (in non-automated scenarios, human operators may be prompted to provide the necessary input) - it makes tests more susceptible to bugs Define a utility method as a consistent and concise way to facilitate the common use case. Require descriptive text via the `intent` parameter in order to encourage test authors to explicitly describe the rationale for requesting additional privileges. [1] https://html.spec.whatwg.org/#triggered-by-user-activation -- wpt-commits: 8b8082f30267410e4b3729439be23df8b803dde8 wpt-pr: 11511
2585105a86c1f40fb675f4bf7f45f804c3e56fbf: Bug 1472242 [wpt PR 11731] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 29 Jun 2018 22:35:56 +0000 - rev 426118
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472242 [wpt PR 11731] - Update wpt metadata, a=testonly wpt-pr: 11731 wpt-type: metadata
51a659edc01aba75e5fa9a0574e92c043655eec1: Bug 1472242 [wpt PR 11731] - Make sure stacking context is always updated for ::first-letter., a=testonly
Rune Lillesveen <futhark@chromium.org> - Fri, 06 Jul 2018 23:49:01 +0000 - rev 426117
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472242 [wpt PR 11731] - Make sure stacking context is always updated for ::first-letter., a=testonly Automatic update from web-platform-testsMake sure stacking context is always updated for ::first-letter. ::first-letter sadly has at least three code paths for computing its computed style. Two of them were lacking stacking context update. There is work in progress for Squad to mend this, but let's fix the current code paths for now. Bug: 856806 Change-Id: Ifeea799643bfa266e58c948f476bc23481fcdd5e Reviewed-on: https://chromium-review.googlesource.com/1120249 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#571512} -- wpt-commits: 02cfdfe53b794884bcd731e18f845bec59dfd707 wpt-pr: 11731
d396738b9fbd95ff2713518fa3015710191553b2: Bug 1472256 [wpt PR 11732] - Update trivial IDL changes, a=testonly
Luke Bjerring <lukebjerring@users.noreply.github.com> - Fri, 06 Jul 2018 23:47:43 +0000 - rev 426116
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472256 [wpt PR 11732] - Update trivial IDL changes, a=testonly Automatic update from web-platform-testsUpdate trivial IDL changes (#11732) -- wpt-commits: 7706fe685052caf0d9295123913ed4a7dddfb6a5 wpt-pr: 11732
610562192785827dbbcc03cbc61663351f08724c: Bug 1472129 [wpt PR 11727] - Fix make_hosts_file tests in python 3., a=testonly
Ms2ger <Ms2ger@gmail.com> - Fri, 06 Jul 2018 23:46:27 +0000 - rev 426115
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1472129 [wpt PR 11727] - Fix make_hosts_file tests in python 3., a=testonly Automatic update from web-platform-testsFix make_hosts_file tests in python 3. (#11727) -- wpt-commits: 75676053b648fbe89988922f357faaa485bb5b88 wpt-pr: 11727
1f8ab1d56b77b50464ca295df1f5ee6d5bd3510e: Bug 1468165 [wpt PR 9796] - Update payment-handler IDL file, a=testonly
Luke Bjerring <lukebjerring@users.noreply.github.com> - Fri, 06 Jul 2018 23:45:10 +0000 - rev 426114
Push 34267 by rgurzau@mozilla.com at Wed, 11 Jul 2018 22:05:21 +0000
Bug 1468165 [wpt PR 9796] - Update payment-handler IDL file, a=testonly Automatic update from web-platform-testsUpdate payment-handler IDL file (#9796) -- wpt-commits: 451270209b02ebade6f0fddd068fab9658f4816e wpt-pr: 9796
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip