1e57e2191f0dd0e922ea68b0b8a41e976d7a2974: Bug 1485060 [wpt PR 12598] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 21 Aug 2018 17:52:01 +0000 - rev 436003
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1485060 [wpt PR 12598] - Update wpt metadata, a=testonly wpt-pr: 12598 wpt-type: metadata
3f6470c8ab4782ef9e384bc16dbe032cea19a200: Bug 1485060 [wpt PR 12598] - [Shadow DOM] Fix test using assert_array_equals, a=testonly
Pierre-Marie Dartus <dartus.pierremarie@gmail.com> - Tue, 11 Sep 2018 10:00:06 +0000 - rev 436002
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1485060 [wpt PR 12598] - [Shadow DOM] Fix test using assert_array_equals, a=testonly Automatic update from web-platform-tests[Shadow DOM] Fix test using assert_array_equals (#12598) Fix occurrences of assert_array_equals where it is used to compare the array length instead of the array itself. https://wpt.fyi/results/shadow-dom/leaktests/get-elements.html?sha=0398567bac https://wpt.fyi/results/shadow-dom/Extensions-to-Event-Interface.html?sha=0398567bac -- wpt-commits: 334fe760e46f7bf64c3a514b0fd6f5ef84da52f5 wpt-pr: 12598
c2ff4ef0946b09717162a824fdea1a1d1fd8b635: Bug 1489591 [wpt PR 12898] - [testharness.js] Reject non-thenable values, a=testonly
jugglinmike <mike@mikepennisi.com> - Tue, 11 Sep 2018 09:59:49 +0000 - rev 436001
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489591 [wpt PR 12898] - [testharness.js] Reject non-thenable values, a=testonly Automatic update from web-platform-tests[testharness.js] Reject non-thenable values (#12898) Previously, any test defined via the `promise_test` API would fail immediately if its body returned the value `undefined`. The test would *not* fail if it returned any other value. Because the motivation for using `promise_test` is to track resolution with a "thenable" value (i.e. an object with a "then" method), this was overly permissive and allowed contributors to write tests which spuriously passed [1]. Update testharness.js to enforce more stringent criteria on the value return by `promise_test` bodies: that it is a "thenable" value. This change is incompatible with an exiting functional test, but it does not effect any tests in WPT (as verified by a survey using both the Chrome and Firefox browsers). Update the functional test accordingly. [1] cca6b6845678d9b5f792b886f3f7045d1d2cf0a7 -- wpt-commits: 86579034357501943927f3dc4abf75d76c477383 wpt-pr: 12898
2734d9b8dd34d1317a652df36643224bd61f4e44: Bug 1489331 [wpt PR 12886] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 07 Sep 2018 23:50:43 +0000 - rev 436000
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489331 [wpt PR 12886] - Update wpt metadata, a=testonly wpt-pr: 12886 wpt-type: metadata
adb23bca8d851a1739889f33a9bfd3303b796984: Bug 1489331 [wpt PR 12886] - Fix calc clamping for font-face descriptors (missed in previous commit), a=testonly
Chris Lilley <chris@w3.org> - Tue, 11 Sep 2018 09:59:30 +0000 - rev 435999
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489331 [wpt PR 12886] - Fix calc clamping for font-face descriptors (missed in previous commit), a=testonly Automatic update from web-platform-testsMerge pull request #12886 from web-platform-tests/FremyCompany-patch-1 Fix calc clamping for font-face descriptors (missed in previous commit) -- wpt-commits: 3eeab8ea5e06da7a927e4c23179728808f6a6e64 wpt-pr: 12886
e469fc908cc9bd763c0da29080ed4f26ad7b8d3d: Bug 1489699 [wpt PR 12903] - CSS: serialize linearRGB and sRGB in lower case, a=testonly
Eric Willigers <ericwilligers@chromium.org> - Tue, 11 Sep 2018 09:59:12 +0000 - rev 435998
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489699 [wpt PR 12903] - CSS: serialize linearRGB and sRGB in lower case, a=testonly Automatic update from web-platform-testsCSS: serialize linearRGB and sRGB in lower case CSS keywords serialize in lower case. https://drafts.csswg.org/cssom/#serializing-css-values "To serialize a CSS component value depends on the component, as follows: keyword The keyword converted to ASCII lowercase." BUG=882014 Change-Id: Ibdfb7f3bf64f26bc4841bbf012668d9071d4473c Reviewed-on: https://chromium-review.googlesource.com/1213563 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#589769} -- wpt-commits: 1c486739d0b8932b4a23ce5ed16936f87fb3b062 wpt-pr: 12903
fde3003a656628c6c3e0834dd1844ca8dcf9928b: Bug 1489599 [wpt PR 12900] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 07 Sep 2018 20:20:16 +0000 - rev 435997
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489599 [wpt PR 12900] - Update wpt metadata, a=testonly wpt-pr: 12900 wpt-type: metadata
94dec1f28de05933d12350e28871c7c6760c0bd5: Bug 1489599 [wpt PR 12900] - Serialize the path() function with double quotes, a=testonly
Fredrik Söderquist <fs@opera.com> - Tue, 11 Sep 2018 09:58:53 +0000 - rev 435996
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489599 [wpt PR 12900] - Serialize the path() function with double quotes, a=testonly Automatic update from web-platform-testsSerialize the path() function with double quotes Per https://drafts.csswg.org/cssom/#serialize-a-string double quotes should be used when serializing strings. Bug: 873527 Change-Id: I3b7a3c6425c6a5d0d6f96399663f5ae8b3929a59 Reviewed-on: https://chromium-review.googlesource.com/1213171 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#589652} -- wpt-commits: 9a5d71b326166e12784bdd9d161772e20f87c1fd wpt-pr: 12900
6cc4109ffbd1f0f060ba1689e3906eceaa27945d: Bug 1489023 [wpt PR 12865] - Fire XHR abort event from a task, a=testonly
Timothy Gu <timothygu@chromium.org> - Tue, 11 Sep 2018 09:58:36 +0000 - rev 435995
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489023 [wpt PR 12865] - Fire XHR abort event from a task, a=testonly Automatic update from web-platform-testsFire XHR abort event from a task A test for this new behavior is included as external/wpt/xhr/abort-after-stop.htm. This also means that XHR abort and readystatechange events from navigation is no longer fired. Because of that, external/wpt/xhr/open-url-multi-window-4.htm now times out rather than fails on an assertion, aligning with Firefox. A TestExpectations entry has been added with a bug that tracks fixing this test in spec or upstream in WPT. A few other test expectations were updated as well to account for this. http/tests/navigation/reentrant-xhr-onabort-crash-during-commit.html no longer works as intended, as abort event is no longer fired synchronously (and thus does not expose the same crash surface). It is replaced with an EventSource-based test that functions the same way as XHR before this CL. Note, currently EventSource's error event suffers from the same problem as XHR's abort event, and the class might undergo the same change as this in the future. We will look into an alternative for this test when that change is done. Bug: 879620, 881180 Change-Id: I5a91047086d06347794656f92511a53c22401b5e Reviewed-on: https://chromium-review.googlesource.com/1208672 Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Timothy Gu <timothygu@chromium.org> Cr-Commit-Position: refs/heads/master@{#589634} -- wpt-commits: 070b8cc14e896cb7d18e0043dbbf9e4c563d9fc0 wpt-pr: 12865
182c1a2dfc6e3648eec54e68241797365c752d25: Bug 1489646 [wpt PR 8894] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=181239, a=testonly
youennf <youennf@users.noreply.github.com> - Tue, 11 Sep 2018 09:57:45 +0000 - rev 435994
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489646 [wpt PR 8894] - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=181239, a=testonly Automatic update from web-platform-testsMerge pull request #8894 from youennf/wpt-export-for-webkit-181239 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=181239 -- wpt-commits: 44e61df7d7132412b70ce8331cada50145387cc3 wpt-pr: 8894
b529794168a2bd96e3aba7c600a3d14eb8a48b9f: Bug 1482156 [wpt PR 12380] - Implement WebDriver executor for wptrunner, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 10 Sep 2018 18:18:27 +0000 - rev 435993
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1482156 [wpt PR 12380] - Implement WebDriver executor for wptrunner, a=testonly Automatic update from web-platform-tests Add WebDriver executor for wptrunner This adds edge_webdriver, chrome_webdriver, and safari_webdriver as products. Co-authored-by: Geoffrey Sneddon <me@gsnedders.com> -- Fix get_test_window in SeleniumExecutor to use the window_id arg -- Clarify comment -- wpt-commits: 9506c250d037996259a8521aeb0d4855913cd078, 82f2a37af56857585cb2bf868ef89eeba7e9b698, 59bed3508ceae6bd16e31971c3d0448d13a5113b wpt-pr: 12380
b3addb97e3e5ca4a7700c584c290d92ed8ac7277: Bug 1489338 [wpt PR 12887] - Slightly improve AudioBuffer resampling, a=testonly
Raymond Toy <rtoy@chromium.org> - Mon, 10 Sep 2018 18:15:50 +0000 - rev 435992
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489338 [wpt PR 12887] - Slightly improve AudioBuffer resampling, a=testonly Automatic update from web-platform-testsSlightly improve AudioBuffer resampling Use simple linear extrapolation to resample the data when we reach the end of the buffer. Previously, the last sample would just be repeated enough times. Manually verified that the test passes on Firefox (nightly) and fails on Chrome without this CL. Bug: 881119 Test: the-audiobuffersourcenode-interface/buffer-resampling.html Change-Id: I1eb6ee089aa5477e03ff7184eb974f769b739528 Reviewed-on: https://chromium-review.googlesource.com/1211910 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#589529} -- wpt-commits: 8764370989723f3166cb8aeee5506e93833aa146 wpt-pr: 12887
8dc164ae68307016777cb9d82ca2fd8aa5f3d6bd: Bug 1489038 [wpt PR 12868] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 06 Sep 2018 08:52:46 +0000 - rev 435991
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489038 [wpt PR 12868] - Update wpt metadata, a=testonly wpt-pr: 12868 wpt-type: metadata
858f51269eb26a23b18264f1e28f2647cc11a4ad: Bug 1489038 [wpt PR 12868] - [css-contain] check the effects of containment on baseline alignment, a=testonly
Florian Rivoal <git@florian.rivoal.net> - Mon, 10 Sep 2018 18:15:30 +0000 - rev 435990
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489038 [wpt PR 12868] - [css-contain] check the effects of containment on baseline alignment, a=testonly Automatic update from web-platform-tests[css-contain] check the effects of containment on baseline alignment (#12868) * [css-contain] check the effects of containment on baseline alignment Tests for https://github.com/w3c/csswg-drafts/issues/2995 Only the layout and size variant are needed to catch know bugs (in chrome) at the time of implementation, and mistakes on paint or style would be surprising, but it doesn't hurt to be exhaustive. -- wpt-commits: 844cecae1ea48d364c5dfb723695354256c13666 wpt-pr: 12868
977177e75fabc38be4ee9cf463e86580cad246ff: Bug 1488245 [wpt PR 12811] - HTML: test how <legend align> does not map to text-align, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 10 Sep 2018 18:15:07 +0000 - rev 435989
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1488245 [wpt PR 12811] - HTML: test how <legend align> does not map to text-align, a=testonly Automatic update from web-platform-testsHTML: test how <legend align> does not map to text-align See https://github.com/whatwg/html/pull/3934 -- wpt-commits: 7fc2450b557f563772fcab4f58c8be7a0ac4d0f1 wpt-pr: 12811
d12098f3d90c245e219e5b66dc5c0502fd48d766: Bug 1489280 [wpt PR 12881] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 07 Sep 2018 09:09:43 +0000 - rev 435988
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489280 [wpt PR 12881] - Update wpt metadata, a=testonly wpt-pr: 12881 wpt-type: metadata
406d478bdc5f5fdb3896c1e77deac1e8d57c014a: Bug 1489280 [wpt PR 12881] - Improve test coverage of registered properties in paint worklets., a=testonly
Anders Hartvoll Ruud <andruud@chromium.org> - Mon, 10 Sep 2018 18:14:47 +0000 - rev 435987
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1489280 [wpt PR 12881] - Improve test coverage of registered properties in paint worklets., a=testonly Automatic update from web-platform-testsImprove test coverage of registered properties in paint worklets. The most important use case for css-properties-values-api is having typed (and possibly interpolated) custom properties in paint worklets. So naturally, this is the *least* well tested use case in WPT. This CL improves that by adding tests for most of the syntax types. The test works as a kind of "ref" test, which compares the output of CSSStyleValue.parse /parseAll with the value observed inside the worklet. <transform-function> and <transform-list> are not supported yet, so they will come later. Interpolations should also be tested, but that belongs in a separate test. Bug: 641877 Change-Id: I4bd310ecd61a2a8989df9c4a5c818cdc7c179b3a Reviewed-on: https://chromium-review.googlesource.com/1209711 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#589461} -- wpt-commits: e5f7af549a9fe9c35191ad3f1ffaa3b02ed47795 wpt-pr: 12881
33923f08e61b1836a62ee69b8df09c9b131b4df7: Bug 1488179 [wpt PR 12801] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 03 Sep 2018 11:08:08 +0000 - rev 435986
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1488179 [wpt PR 12801] - Update wpt metadata, a=testonly wpt-pr: 12801 wpt-type: metadata
de87d57a04c11fff1aee7f2805ce0600086f1692: Bug 1488179 [wpt PR 12801] - HTML: test that focus() on legend does not delegate focus, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 10 Sep 2018 18:14:27 +0000 - rev 435985
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1488179 [wpt PR 12801] - HTML: test that focus() on legend does not delegate focus, a=testonly Automatic update from web-platform-tests HTML: test that focus() on legend does not delegate focus See https://github.com/whatwg/html/issues/3950 -- wpt-commits: 910a8da21bb508cc774ae1acf9ead70f119ebb97 wpt-pr: 12801
0ede957914c48b05a03cf9f754cbd9dfc4cad057: Bug 1488178 [wpt PR 12800] - HTML: test accesskey for legend, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 10 Sep 2018 18:14:10 +0000 - rev 435984
Push 34625 by dvarga@mozilla.com at Thu, 13 Sep 2018 02:31:40 +0000
Bug 1488178 [wpt PR 12800] - HTML: test accesskey for legend, a=testonly Automatic update from web-platform-testsHTML: test accesskey for legend See https://github.com/whatwg/html/pull/3987 -- wpt-commits: de955843cde5540bfc63015490630beeb1f19f89 wpt-pr: 12800
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip