41547769990900a9be115e028282f9cb8b9aa987: Bug 1452593 [wpt PR 10356] - Properly define EventInit in /webvr/idlharness.https.html, a=testonly
Anthony Ramine <n.oxyde@gmail.com> - Mon, 09 Apr 2018 22:35:32 +0000 - rev 413803
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452593 [wpt PR 10356] - Properly define EventInit in /webvr/idlharness.https.html, a=testonly Automatic update from web-platform-testsProperly define EventInit in /webvr/idlharness.https.html wpt-commits: 2b8e0e7004fa407892b0966d2ae3d1ce68aaf678 wpt-pr: 10356 wpt-commits: 2b8e0e7004fa407892b0966d2ae3d1ce68aaf678 wpt-pr: 10356
4d895b739d93c3f042cb91a6ab5c071939a13252: Bug 1451994 [wpt PR 10340] - service worker: Add tests for inteception of workers after redirects., a=testonly
Matt Falkenhagen <falken@chromium.org> - Mon, 09 Apr 2018 22:34:56 +0000 - rev 413802
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1451994 [wpt PR 10340] - service worker: Add tests for inteception of workers after redirects., a=testonly Automatic update from web-platform-testsservice worker: Add tests for inteception of workers after redirects. This tests behavior discussed here: https://github.com/w3c/ServiceWorker/issues/1289 Namely it tests when a request for a worker goes through a redirect chain: 1) On redirect from A -> B, whether the service worker at B sees the request. 2) After the final redirect, which service worker controls the resulting client. The tests are written as specified today. Therefore, Firefox passes this test (verified in Nightly) and Chrome does not. (Actually a small change is required to the test to make Firefox pass it, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1452528) Currently it only tests shared worker but dedicated worker can be added in a follow-up patch. Bug: 829720 Change-Id: Id3b1ea8b952760be0ef9917f2c6a3afe60ca1fb5 Reviewed-on: https://chromium-review.googlesource.com/999241 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#549125} wpt-commits: 6fe36d79072d5261ea504435b0dfedaf39f5805a wpt-pr: 10340 wpt-commits: 6fe36d79072d5261ea504435b0dfedaf39f5805a wpt-pr: 10340
0b20cccaed6e6890823b8daad46167e0c89f8667: Bug 1443103 [wpt PR 9800] - Correct serialization of box-shadow and text-shadow, a=testonly
Chris Nardi <christopherncarmel@hotmail.com> - Mon, 09 Apr 2018 22:34:28 +0000 - rev 413801
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1443103 [wpt PR 9800] - Correct serialization of box-shadow and text-shadow, a=testonly Automatic update from web-platform-testsCorrect serialization of box-shadow and text-shadow Following https://github.com/w3c/csswg-drafts/issues/2305, the canonical serialization for box-shadow was changed to the color then lengths. https://drafts.csswg.org/css-text-decor-3/#text-shadow-property also defines the canonical serialization for text-shadow as the color and then lengths. This caused the test to fail in Firefox, Chrome, and Safari. Update the test to match the spec in both instances. wpt-commits: a835486e59a94236a55107fe34925079b33ef247 wpt-pr: 9800 wpt-commits: a835486e59a94236a55107fe34925079b33ef247 wpt-pr: 9800
c2c7dccc2545cdf93f4746fb728097603c8c851d: Bug 1452590 [wpt PR 10358] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 09 Apr 2018 12:53:17 +0000 - rev 413800
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452590 [wpt PR 10358] - Update wpt metadata, a=testonly wpt-pr: 10358 wpt-type: metadata
b997f18f956804577fd2a6531b9dbbb3a4cc9781: Bug 1452590 [wpt PR 10358] - Sync Mozilla tests as of 2018-04-08, a=testonly
L. David Baron <dbaron@dbaron.org> - Mon, 09 Apr 2018 22:33:54 +0000 - rev 413799
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452590 [wpt PR 10358] - Sync Mozilla tests as of 2018-04-08, a=testonly Automatic update from web-platform-testsSync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/b4bc6b2401738b78fd47127a4c716bb9178e1a09 . (#10358) wpt-commits: 8f9d8e97bc197888e5f396f971e1c5e7c83f11b3 wpt-pr: 10358 wpt-commits: 8f9d8e97bc197888e5f396f971e1c5e7c83f11b3 wpt-pr: 10358
b108edd5128d767d3cfaeaabdb2bbdcdbc99e0de: Bug 1451194 [wpt PR 10301] - [css-typed-om] Implement support for text-* properties., a=testonly
Darren Shen <shend@chromium.org> - Mon, 09 Apr 2018 22:33:23 +0000 - rev 413798
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1451194 [wpt PR 10301] - [css-typed-om] Implement support for text-* properties., a=testonly Automatic update from web-platform-tests[css-typed-om] Implement support for text-* properties. There's a failing test due to Blink computing keyword values for text-size-adjust to percentages, even though the spec says the computed value is as specified. Bug: 820299 Change-Id: I53c4177f1ce2205a4f2b6af00b1c61da4f5e774f Reviewed-on: https://chromium-review.googlesource.com/994594 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#549095} wpt-commits: 8a4cdaf6df416d33c0b2cb591fb078d7448591db wpt-pr: 10301 wpt-commits: 8a4cdaf6df416d33c0b2cb591fb078d7448591db wpt-pr: 10301
2c288bfe481e9c0cd6d57d0bdec8e79061e4b7b3: Bug 1452484 [wpt PR 10361] - Remove SimonSapin from OWNERS, a=testonly
Simon Sapin <simon.sapin@exyr.org> - Mon, 09 Apr 2018 22:32:55 +0000 - rev 413797
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452484 [wpt PR 10361] - Remove SimonSapin from OWNERS, a=testonly Automatic update from web-platform-testsRemove SimonSapin from OWNERS (#10361) wpt-commits: 318f2876ef4b288bb805f855c679dc1b583d8475 wpt-pr: 10361 wpt-commits: 318f2876ef4b288bb805f855c679dc1b583d8475 wpt-pr: 10361
0b7049a25f7590571b33fb445f3bb57054c92c9c: Bug 1452482 [wpt PR 10360] - Adapt web-nfc IDL tests to latest spec, a=testonly
kaixinjxq <xiuqix.jiang@intel.com> - Mon, 09 Apr 2018 22:32:27 +0000 - rev 413796
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452482 [wpt PR 10360] - Adapt web-nfc IDL tests to latest spec, a=testonly Automatic update from web-platform-testsAdapt web-nfc IDL tests to latest spec (#10360) wpt-commits: f16180450896438c055fe41c16a5d26593d15b6d wpt-pr: 10360 wpt-commits: f16180450896438c055fe41c16a5d26593d15b6d wpt-pr: 10360
291cf72732db4c39939013dcf4376b0847c7965e: Bug 1452481 [wpt PR 10353] - Update expected cssText for custom property serialization, a=testonly
Chris Nardi <christopherncarmel@hotmail.com> - Mon, 09 Apr 2018 22:31:59 +0000 - rev 413795
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452481 [wpt PR 10353] - Update expected cssText for custom property serialization, a=testonly Automatic update from web-platform-testsUpdate expected cssText for custom property serialization See https://github.com/w3c/csswg-drafts/issues/2509#issuecomment-379152590 for the change to target9. Also remove the extra whitespace in target8 and target1 which causes these tests to fail in Chrome and Firefox. Also remove testcase.propertyName from each test's name as this doesn't exist and just outputs undefined. wpt-commits: d0d62244432d329aa22e9278d3e83184301c3e7f wpt-pr: 10353 wpt-commits: d0d62244432d329aa22e9278d3e83184301c3e7f wpt-pr: 10353
ca4d8311c5ad935a0e9c289d061f6da3d5f9317e: Bug 1452325 [wpt PR 10336] - Improve idlharness error message for exposure test, a=testonly
Luke Bjerring <lukebjerring@users.noreply.github.com> - Mon, 09 Apr 2018 22:31:23 +0000 - rev 413794
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452325 [wpt PR 10336] - Improve idlharness error message for exposure test, a=testonly Automatic update from web-platform-testsImprove idlharness error message for exposure test (#10336) When `obj` is not created successfully, there's an error like > Cannot use 'in' operator to search for [member.name] in undefined NB: I'm not a fan of having each sub-test re-test the same thing, but this is at least _consistent_ with the other code.. wpt-commits: 6e68c444ed00317ee7035fd2e1e144eb4a6a6091 wpt-pr: 10336 wpt-commits: 6e68c444ed00317ee7035fd2e1e144eb4a6a6091 wpt-pr: 10336
0e70c75623c67aaf67c51b5ce308958c3823a89b: Bug 1452323 [wpt PR 10349] - Cookie Store: Tentatively deflake special names test, a=testonly
Joshua Bell <jsbell@chromium.org> - Mon, 09 Apr 2018 22:30:55 +0000 - rev 413793
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452323 [wpt PR 10349] - Cookie Store: Tentatively deflake special names test, a=testonly Automatic update from web-platform-testsCookie Store: Tentatively deflake special names test The "expires" cases are flaky on all platforms on the bots, although I can't reproduce locally. The test case sets a cookie that expires "now" then expects it can't read it. It may be flaky due to "now" being slightly different between processes, threads, and libraries, allowing the read to succeed. Set the expiry date to be an hour before "now", which should be sufficient. Bug: 829761 Change-Id: Icda1891310dd0a56769877f32405226390e729de Reviewed-on: https://chromium-review.googlesource.com/999743 Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#548903} wpt-commits: a4c17db5364ca97ffa9bb76f9c8e6e155ecd3ddb wpt-pr: 10349 wpt-commits: a4c17db5364ca97ffa9bb76f9c8e6e155ecd3ddb wpt-pr: 10349
16b585bde69a0a9b7d4ce839bbbe4b676da17de4: Bug 1452320 [wpt PR 10320] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 08 Apr 2018 22:59:38 +0000 - rev 413792
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452320 [wpt PR 10320] - Update wpt metadata, a=testonly wpt-pr: 10320 wpt-type: metadata
bce11426a95e4edc9f7e7461089f93ffe1051545: Bug 1452320 [wpt PR 10320] - Move AudioNode tests to WPT, a=testonly
Raymond Toy <rtoy@chromium.org> - Mon, 09 Apr 2018 22:30:19 +0000 - rev 413791
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452320 [wpt PR 10320] - Move AudioNode tests to WPT, a=testonly Automatic update from web-platform-testsMove AudioNode tests to WPT Move the AudioNode tests to WPT. Can't move tail-processing.html because it's specific to Chrome's tail processing. Firefox passes all tests except: * audionode.html (because new AudioContext(1,44100,44100) succeeds but shouldn't * tests that use oac.suspend * audionode-connect-method-chaining.html with an IndexSizeError connecting Bug: 745778 Change-Id: I0e21e2117a75246367ea2642759ed917ee3e028f Reviewed-on: https://chromium-review.googlesource.com/994136 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Reviewed-by: Dirk Pranke <dpranke@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#548843} wpt-commits: 68b07988d40f8a0250675fd0de3c6ae96921608e wpt-pr: 10320 wpt-commits: 68b07988d40f8a0250675fd0de3c6ae96921608e wpt-pr: 10320
4b387daaf7deaee185cdcc0c8e9aa68c3aa2cc43: Bug 1452316 [wpt PR 10346] - Update mozrunner to 6.15, a=testonly
pyup.io bot <github-bot@pyup.io> - Mon, 09 Apr 2018 22:29:43 +0000 - rev 413790
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452316 [wpt PR 10346] - Update mozrunner to 6.15, a=testonly Automatic update from web-platform-testsUpdate mozrunner from 6.14 to 6.15 (#10346) wpt-commits: ea9348739755aa9bac698f8032ec73d02bc2174a wpt-pr: 10346 wpt-commits: ea9348739755aa9bac698f8032ec73d02bc2174a wpt-pr: 10346
3c8a0973bc175a59fa0fb0b68440c8ac6d0408db: Bug 1452315 [wpt PR 10298] - Cookie Store: rework tests for 'expires' option, a=testonly
Joshua Bell <jsbell@chromium.org> - Mon, 09 Apr 2018 22:29:15 +0000 - rev 413789
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452315 [wpt PR 10298] - Cookie Store: rework tests for 'expires' option, a=testonly Automatic update from web-platform-testsCookie Store: rework tests for 'expires' option Simplify/rework the tests for the 'expires' options. Don't run the tests with the special secure-only prefixes, as that's orthogonal to the behvior. In Chromium, this also reveals that support for HTTP date strings as 'expires' values, as described in the explainer[1] is not yet supported. [1] https://github.com/WICG/cookie-store/blob/gh-pages/explainer.md Bug: 729800 Change-Id: I015fd643f18b59c8294f9dc62d576682132795fd Reviewed-on: https://chromium-review.googlesource.com/994284 Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#548818} wpt-commits: 8b9501b721963f2b3886f25e20f17a2afe6bc381 wpt-pr: 10298 wpt-commits: 8b9501b721963f2b3886f25e20f17a2afe6bc381 wpt-pr: 10298
04639022a761c8731ff1eef60b124935df809765: Bug 1450905 [wpt PR 10277] - Update ReadableStream to latest standard version, a=testonly
Adam Rice <ricea@chromium.org> - Mon, 09 Apr 2018 22:28:47 +0000 - rev 413788
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1450905 [wpt PR 10277] - Update ReadableStream to latest standard version, a=testonly Automatic update from web-platform-testsUpdate ReadableStream to latest standard version Update Blink's implementation of ReadableStream to https://streams.spec.whatwg.org/commit-snapshots/37ace3d5f16cbea7aec4a0c80532c95059994d51/ This also updates TransformStream to use CreateReadableStream() instead of calling the ReadableStream constructor. Several common operations have become unused and have been removed. The EXTERNALLY_CONTROLLED flag has been renamed to the slightly more specific name "BLINK_LOCK_NOTIFICATIONS". All external/wpt/streams/readable-streams tests now pass, and failing expectations have been removed. Most changes were already covered by the web-platform-tests. A new readable-streams/patched-global.js test verifies that ReadableStreamTee() does not use the global ReadableStream constructor or otherwise touch the global object. BUG=710728 Change-Id: I2b799045f47376adef305f5f88ad106161425b46 Reviewed-on: https://chromium-review.googlesource.com/992077 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#548784} wpt-commits: 8314b7b5ae86ebf5bc435558ae5b0af32b1d7756 wpt-pr: 10277 wpt-commits: 8314b7b5ae86ebf5bc435558ae5b0af32b1d7756 wpt-pr: 10277
f1e731ebb6bb0614bb31f287112ef2c320925a25: Bug 1451904 [wpt PR 10339] - Fix the |name| of PerformanceNavigationTiming, a=testonly
Nicolas Pena <npm@chromium.org> - Mon, 09 Apr 2018 22:28:19 +0000 - rev 413787
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1451904 [wpt PR 10339] - Fix the |name| of PerformanceNavigationTiming, a=testonly Automatic update from web-platform-testsFix the |name| of PerformanceNavigationTiming Previously, the |name| of a PerformanceNavigationTiming entry was the initial URL (the request URL). After this CL, it is the response URL, so for example a url of the form 'redirect?location=newLoc' will have 'newLoc' as the |name|. Bug: 797465 Change-Id: Icab53ad8027d066422562c82bcf0354c264fea40 Reviewed-on: https://chromium-review.googlesource.com/996579 Reviewed-by: Yoav Weiss <yoav@yoav.ws> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#548773} wpt-commits: a0091fbff26091db1fd4b6ca07d9512edf7e6a95 wpt-pr: 10339 wpt-commits: a0091fbff26091db1fd4b6ca07d9512edf7e6a95 wpt-pr: 10339
21f189e1f5c9894fda096f7ad04b180c39ae47fa: Bug 1447862 [wpt PR 10130] - Make BlueTooth/USB requestDevice non-consuming., a=testonly
Mustaq Ahmed <mustaq@google.com> - Mon, 09 Apr 2018 22:27:51 +0000 - rev 413786
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1447862 [wpt PR 10130] - Make BlueTooth/USB requestDevice non-consuming., a=testonly Automatic update from web-platform-testsMake BlueTooth/USB requestDevice non-consuming. The specs for both WebBlueTooth & WebUSB only require a user activation during a requestDevice call. So consuming the activation (vs just checking) is not a strong requirement. There was a concern that "not consuming" could possibly mean multiple choosers for a single user activation but our browser code already handles the situation gracefully. Multiple requests to browser is possible from different tabs anyway, even with (isolated) consumptions in individual tabs. Therefore it makes sense to remove the consumption behavior here, which is not spec-ed anyway. This would fit our goal of a simple user activation model ("UserActivationV2" project) which should be simple enough for cross-browser implementation and for a complete spec. Bug: 786407 Change-Id: I3c9dbf43df34d4cb4a2a33214a6c44847fa7435b Reviewed-on: https://chromium-review.googlesource.com/775866 Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> Cr-Commit-Position: refs/heads/master@{#548768} wpt-commits: 6ba01ea2ffbafbb329352628b244815654b38156 wpt-pr: 10130 wpt-commits: 6ba01ea2ffbafbb329352628b244815654b38156 wpt-pr: 10130
1729ff1996d7ec2fa37729e591edf7950ccedaf1: Bug 1452343 [wpt PR 9753] - Update the FileAPI IDL file, a=testonly
Luke Bjerring <lukebjerring@users.noreply.github.com> - Mon, 09 Apr 2018 22:27:22 +0000 - rev 413785
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452343 [wpt PR 9753] - Update the FileAPI IDL file, a=testonly Automatic update from web-platform-testsAdd FileAPI idl file (#9753) wpt-commits: 0cddb6844a669459eb30f0bcf175e16e38af2a54 wpt-pr: 9753 wpt-commits: 0cddb6844a669459eb30f0bcf175e16e38af2a54 wpt-pr: 9753
50b93b65b4b0376f0d893cc4f21b9b0322f8f662: Bug 1452314 [wpt PR 10337] - Improve error message for exposure_set test, a=testonly
Luke Bjerring <lukebjerring@users.noreply.github.com> - Mon, 09 Apr 2018 22:26:57 +0000 - rev 413784
Push 33850 by apavel@mozilla.com at Mon, 16 Apr 2018 09:53:48 +0000
Bug 1452314 [wpt PR 10337] - Improve error message for exposure_set test, a=testonly Automatic update from web-platform-testsImprove error message for exposure_set test `memberName` is undefined; error message is (was) `ReferenceError: memberName is not defined`. Clearly supposed to be a check for duplication - `array.length < 0` was a really weird thing to see, though. Spec says it's always non-negative, so deleted that. Error I see now is "Multiple 'Exposed' extended attributes on Navigator" wpt-commits: 6dd31359159f88202ef73da68c4ad2eef2a3bc99 wpt-pr: 10337 wpt-commits: 6dd31359159f88202ef73da68c4ad2eef2a3bc99 wpt-pr: 10337
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip