5395db370569cbf4988ce37b4f3016d5cfbcb2b9: Bug 1514432 [wpt PR 14530] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 15 Dec 2018 14:13:11 +0000 - rev 454933
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514432 [wpt PR 14530] - Update wpt metadata, a=testonly wpt-pr: 14530 wpt-type: metadata
4bfef6168f182fd75312c7194bb26b7441188442: Bug 1514432 [wpt PR 14530] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706, a=testonly
youennf <youennf@users.noreply.github.com> - Wed, 19 Dec 2018 12:09:17 +0000 - rev 454932
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514432 [wpt PR 14530] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192706 (#14530) -- wpt-commits: e183d8671bde035c7a0168a75119a5f80bd592cb wpt-pr: 14530
86ca0a729bfcfa8a0d8c0e223fd6285b682bb600: Bug 1513766 [wpt PR 14486] - [CSS Transitions] Add test for reparenting, a=testonly
Stephen McGruer <smcgruer@chromium.org> - Wed, 19 Dec 2018 12:09:15 +0000 - rev 454931
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513766 [wpt PR 14486] - [CSS Transitions] Add test for reparenting, a=testonly Automatic update from web-platform-tests [CSS Transitions] Add test for reparenting As per https://github.com/w3c/csswg-drafts/issues/3309, any CSS Transition on a reparented element should be cancelled, as it leaves and then re-enters the Document. This already works on Chrome, Firefox, and Safari but fails on Edge. Bug: 902328 Change-Id: I097675a8146c8047417dd48193d0747216418cfb Reviewed-on: https://chromium-review.googlesource.com/c/1374742 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#616830} -- wpt-commits: cf8b055289c68215fd4a3274c94d0f5484c27dd3 wpt-pr: 14486
a56d3fa354af52ee057e09349d5b0c744af24099: Bug 1514102 [wpt PR 14511] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Dec 2018 10:06:14 +0000 - rev 454930
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514102 [wpt PR 14511] - Update wpt metadata, a=testonly wpt-pr: 14511 wpt-type: metadata
bfd4b93ba923d4bb6746f8246656974c432ed785: Bug 1514102 [wpt PR 14511] - [UserTiming] Fix mark-measure-return-null test, a=testonly
Nicolas Pena <npm@chromium.org> - Wed, 19 Dec 2018 12:09:10 +0000 - rev 454929
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514102 [wpt PR 14511] - [UserTiming] Fix mark-measure-return-null test, a=testonly Automatic update from web-platform-tests [UserTiming] Fix mark-measure-return-null test The test was incorrect per L2 spec: a void method 'returns' an undefined value, not a null object. This CL changes the test to show how to perform feature detection and compares L2 and L3 behavior. Bug: 914441 Change-Id: Id7173b2693d5bd42013dcdd25266d64fa8956e6a -- Merge pull request #14511 from web-platform-tests/chromium-export-cl-1377129 [UserTiming] Fix mark-measure-return-null test -- wpt-commits: 1dd43edb91fa86dbda5af3a9675e3b103c9e8cd0, ca3a8d6d2de5be8dac1daa17126d8f30d1489c95 wpt-pr: 14511
58bbc72bb0ff922171edbc4458b8703cc9808935: Bug 1514001 [wpt PR 14506] - Reland Make testharness tests run in a top-level browsing context , a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 19 Dec 2018 11:52:20 +0000 - rev 454928
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514001 [wpt PR 14506] - Reland Make testharness tests run in a top-level browsing context , a=testonly Automatic update from web-platform-tests Make testharness tests run in a top-level browsing context Traditionally testharness tests ran in a auxillary browsing context opened using window.open and with access to the opener. This works well because the long-lived nature of the opener helps to avoid some of the race conditions that would otherwise occur. But it doesn't work *that* well; the recent refactor to stop continually focusing the opener broke tests that alter document.domain or otherwise prevent the opener being same-domain with the test window. And future platform features may cause the opener to be nulled out entirely so even a postMessage based fix wouldn't work. To solve all of this, this patch refactors things so that the initial window doesn't contain any logic at all and is just used to keep the browser alive between tests. Most of the logic moves to testharnessreport.js which is loaded once per test. In order to get the right timeout when timeout_multiplier is set this requires an addition to the product API in wptrunner to expose a function for getting the timeout multiplier. This allows us to get the timeout_multiplier for testharness tests upfront and avoids the need to change the content of testharnessreport when we start running testharness tests, or to restart the server for each test type. The main issue with the single-window implementation is that we need to start injecting script once the test page has loaded testharnessreport.js. For most browsers we are able to use pageLoadStrategy=eager to control this; in that case we can start running tests once DOMContentLoaded is reached. Chrome doesn't support this pageLoadStrategy, however, so we have to fake support with custom script. -- Ensure we call __wptrunner_process_next_event whenever we put a message on the queue -- wpt-commits: e4ba26cf0324af4ffd46607b296f5362243728a3, f6c42824add97dac84434c92c606aacd867c3534 wpt-pr: 14506
7d98c8a039785005556251fe5d4b7dcaa4050a27: Bug 1514355 [wpt PR 14525] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Dec 2018 20:14:11 +0000 - rev 454927
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514355 [wpt PR 14525] - Update wpt metadata, a=testonly wpt-pr: 14525 wpt-type: metadata
5b91140384aa46aaf31c87d28b19bbdb30b2e3e5: Bug 1514355 [wpt PR 14525] - [LayoutTest] Split animations-parsing.html into two tests, a=testonly
Xida Chen <xidachen@chromium.org> - Wed, 19 Dec 2018 11:39:11 +0000 - rev 454926
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514355 [wpt PR 14525] - [LayoutTest] Split animations-parsing.html into two tests, a=testonly Automatic update from web-platform-tests [LayoutTest] Split animations-parsing.html into two tests Currently it tests both style.animation and getComputedStyle.animation. This CL splits the test into two tests, one for style.animation, and the other one for getComputedStyle.animation such that each test is minimal. Bug: 772852 Change-Id: I3c3f43305497ffe9d91c4e3806efe2e65ff17806 Reviewed-on: https://chromium-review.googlesource.com/c/1378230 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#616677} -- wpt-commits: 3a8ff1cd2f78d58de6ddf4ac0fe13e72e6502229 wpt-pr: 14525
ba204a073a2338fa4f26e97c72361a14d78280a1: Bug 1514365 [wpt PR 14527] - Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html, a=testonly
Fredrik Söderquist <fs@opera.com> - Wed, 19 Dec 2018 11:39:09 +0000 - rev 454925
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514365 [wpt PR 14527] - Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html, a=testonly Automatic update from web-platform-tests Add reftest-wait to css/filter-effects/svg-sourcegraphic-currentcolor-dynamic-001.html Attempt to stabilize in Gecko. Bug: 626744 Change-Id: Idfa06176948d1ffaf6ba8e65263bf5818ffd321b Reviewed-on: https://chromium-review.googlesource.com/c/1375875 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#616543} -- wpt-commits: 4559dab34174df979b5db4d3ba01429c03c06850 wpt-pr: 14527
8058715443bee2dab11a3184042e2b09378896ad: Bug 1513971 [wpt PR 14502] - Regression test for crbug.com/626744, a=testonly
Fredrik Söderquist <fs@opera.com> - Wed, 19 Dec 2018 11:39:07 +0000 - rev 454924
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513971 [wpt PR 14502] - Regression test for crbug.com/626744, a=testonly Automatic update from web-platform-tests Regression test for crbug.com/626744 Bug: 626744 Change-Id: I4244c3f0316ceb55bc69655212f6677345b0a6cc Reviewed-on: https://chromium-review.googlesource.com/c/1374988 Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#616311} -- wpt-commits: ceebcb87c70c4015c585754260384a7ccf7ae219 wpt-pr: 14502
42f5aecff24a2aee8ce97f46552c612934b00591: Bug 1514329 [wpt PR 14523] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 15 Dec 2018 04:03:52 +0000 - rev 454923
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514329 [wpt PR 14523] - Update wpt metadata, a=testonly wpt-pr: 14523 wpt-type: metadata
4c026d2d70bb05c4678e8ca1e0b6dfc4eae614ae: Bug 1514329 [wpt PR 14523] - Use StyleColor for the stop-color property, a=testonly
Fredrik Söderquist <fs@opera.com> - Wed, 19 Dec 2018 11:39:02 +0000 - rev 454922
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514329 [wpt PR 14523] - Use StyleColor for the stop-color property, a=testonly Automatic update from web-platform-tests Use StyleColor for the stop-color property This changes the ComputedStyle storage for the stop-color property to be a StyleColor rather than a plain color. This fixes explicit inheritance for the property ('currentcolor' computes to itself). It also means we'll properly pick up changes to 'color'. Bug: 914728 Change-Id: I3c78a3615220b9149d1ea5102a6e5863526a6d51 Reviewed-on: https://chromium-review.googlesource.com/c/1377437 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#616660} -- wpt-commits: 8a97b8ab9a745f316400585b5e8ac473886f92d0 wpt-pr: 14523
99367c132437d215b047e387ea7706b8b8adf055: Bug 1514115 [wpt PR 14514] - [wptrunner] Correct support for eager page loading, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Wed, 19 Dec 2018 11:39:01 +0000 - rev 454921
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514115 [wpt PR 14514] - [wptrunner] Correct support for eager page loading, a=testonly Automatic update from web-platform-tests [wptrunner] Correct support for eager page loading Many reftests schedule behavior to occur when the document reaches the "complete" readyState by setting the `onload` property of the document element. Previously, the automation scripts were written to conditionally defer execution for that event by setting the `onload` property of the global object. The two strategies are mutually exclusive. The sequence of script execution is not controlled, so either consumer of the "load" event could be blocked by the other. Update the automation scripts to register for the event using `addEventListener` in order to avoid unintended interaction with test code. -- wpt-commits: 6c14d36f4ec7979c459a9636a9c086cc486d43da wpt-pr: 14514
b045963550e9f625040b09269ab61985cd1564af: Bug 1513006 [wpt PR 14438] - Update requests to 2.21.0, a=testonly
pyup-bot <github-bot@pyup.io> - Wed, 19 Dec 2018 11:38:58 +0000 - rev 454920
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513006 [wpt PR 14438] - Update requests to 2.21.0, a=testonly Automatic update from web-platform-tests Update requests from 2.20.1 to 2.21.0 -- wpt-commits: 506442fed41ae8617a030a7d6c64381e97d3a33e wpt-pr: 14438
a6529b88b34accd5201c56d607d6b262dbe6c4ff: Bug 1513654 [wpt PR 14480] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 13 Dec 2018 00:12:28 +0000 - rev 454919
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513654 [wpt PR 14480] - Update wpt metadata, a=testonly wpt-pr: 14480 wpt-type: metadata
b8d762f13655ee9abb526783d38533a45e5e8ed8: Bug 1513654 [wpt PR 14480] - Serialize animation in the right order, a=testonly
Xida Chen <xidachen@chromium.org> - Wed, 19 Dec 2018 11:38:54 +0000 - rev 454918
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513654 [wpt PR 14480] - Serialize animation in the right order, a=testonly Automatic update from web-platform-tests Serialize animation in the right order Per spec: https://drafts.csswg.org/css-animations/#animation The name of the animation should be the end of the value list, to avoid ambiguity when serializing/deserializing the animation. This CL fixes the problem for both element.style and the window.getComputedStyle. A wpt test is added. Since this CL changes the output of an existing web API, an Intent to Ship has been sent to blink-dev and 3 LGTMs has been granted. https://groups.google.com/a/chromium.org/forum/?utm_medium=email&utm_source=footer#!msg/blink-dev/KUelGRZP73Y/F4YxTGBOBwAJ Bug: 772852 Change-Id: I88b06b57c68013d99c8c4fd4bd39bdfcf9b807fc Reviewed-on: https://chromium-review.googlesource.com/c/1367935 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#616639} -- wpt-commits: f378387ce241c01f959467cc4c755459fc705e30 wpt-pr: 14480
98fb4602eafcd498d30b8b76e6c2dcb000b647c1: Bug 1514224 [wpt PR 14521] - Ignore adopted stylesheets from different document tree, a=testonly
Rakina Zata Amni <rakina@chromium.org> - Wed, 19 Dec 2018 11:38:46 +0000 - rev 454917
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514224 [wpt PR 14521] - Ignore adopted stylesheets from different document tree, a=testonly Automatic update from web-platform-tests Ignore adopted stylesheets from different document tree If we adopt a subtree containing a shadowRoot that has adoptedStyleSheets from one document to a different document, the adoptedStyleSheets will be moved along with it. We want to ignore the stylesheets that are constructed in a different document tree when we're doing style calculation. Draft spec: https://wicg.github.io/construct-stylesheets/ Bug: 807560 Change-Id: If36676e642b5d1b5c1c403c14cc24be8e670f153 Reviewed-on: https://chromium-review.googlesource.com/c/1377486 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#616621} -- wpt-commits: 15886f09cbd3a09599452ab5571cc5396ea23f66 wpt-pr: 14521
d933e877b8663038681e281d4c2dc5549d2c3a78: Bug 1514125 [wpt PR 14516] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192685, a=testonly
youennf <youennf@users.noreply.github.com> - Wed, 19 Dec 2018 11:38:43 +0000 - rev 454916
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1514125 [wpt PR 14516] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192685, a=testonly Automatic update from web-platform-tests WebKit export of https://bugs.webkit.org/show_bug.cgi?id=192685 (#14516) -- wpt-commits: 1db8f79ee94cf257617cbf470c6dcf7e0bbdcab5 wpt-pr: 14516
c313f303498ae59a09f686d792b90e49e8b6a9ae: Bug 1513989 [wpt PR 14504] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 14 Dec 2018 01:22:58 +0000 - rev 454915
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513989 [wpt PR 14504] - Update wpt metadata, a=testonly wpt-pr: 14504 wpt-type: metadata
f3338f6cf9696139af3e57653451e7915e088dd6: Bug 1513989 [wpt PR 14504] - Return used width/height for SVG <image>, <rect> and <foreignObject>, a=testonly
Fredrik Söderquist <fs@opera.com> - Wed, 19 Dec 2018 11:38:38 +0000 - rev 454914
Push 111373 by james@hoppipolla.co.uk at Wed, 23 Jan 2019 11:17:29 +0000
Bug 1513989 [wpt PR 14504] - Return used width/height for SVG <image>, <rect> and <foreignObject>, a=testonly Automatic update from web-platform-tests Return used width/height for SVG <image>, <rect> and <foreignObject> Per https://drafts.csswg.org/cssom/#resolved-values we should return the "used value" for 'width' and 'height' on these elements [1]. This behavior was clarified in SVGWG GitHub issue #349 [2]. [1] And also on <svg>, but we don't support those properties there yet. Tests added for that case too though. [2] https://github.com/w3c/svgwg/issues/349 Bug: 772707 Change-Id: Ic7b6b148883d4380daadb41b62bddd02da55e1af Reviewed-on: https://chromium-review.googlesource.com/c/1374291 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#616343} -- wpt-commits: e75e7b667c75aabc4569b46d902b81d40d9b8e44 wpt-pr: 14504
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip