Skip to main content

Browse the archive

https://github.com/web-platform-tests/wpt
26 December 2018, 22:31:15 UTC
sort by:
Revision Author Date Message Commit Date
5423d8e Mike Pennisi 12 September 2018, 23:30:20 UTC Demonstrate on downstream fork 10 December 2018, 18:45:51 UTC
e33bc4d James Graham 07 November 2018, 13:09:19 UTC Remove reference to missing run() function in CSS tests 10 December 2018, 18:45:39 UTC
b538b78 James Graham 07 November 2018, 13:08:04 UTC Fix document.write tests to not assume globals exist after document.open 10 December 2018, 18:45:39 UTC
e7b12a2 James Graham 05 November 2018, 17:55:24 UTC 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. 10 December 2018, 18:45:39 UTC
8eab58f jugglinmike 10 December 2018, 18:31:21 UTC [WebCryptoAPI] Remove race condition (#14291) * [WebCryptoAPI] Remove race condition Configure testharness.js to wait until the global `done` function is invoked before reporting results. This ensures that all asynchronously-declared tests are defined and subsequently executed regardless of variations in timing. * fixup! [WebCryptoAPI] Remove race condition 10 December 2018, 18:31:21 UTC
ee999c2 Harald Alvestrand 10 December 2018, 16:39:30 UTC Add WPT tests for correct parsing of msid Bug: None Change-Id: Ib12aa3660a1b1d2c350d7fd81aaff810b3d979cc Reviewed-on: https://chromium-review.googlesource.com/c/1365443 Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#615145} 10 December 2018, 16:47:56 UTC
e177591 Stephen McGruer 10 December 2018, 16:35:00 UTC [ScrollTimeline] Upstream NaN currentTime tests to WPT This CL upstreams the NaN related currentTime tests to WPT. There are no behavioral changes. Bug: 911254 Change-Id: Ide27accae72cc55654890754ac404c7827889d09 Reviewed-on: https://chromium-review.googlesource.com/c/1366264 Reviewed-by: Majid Valipour <majidvp@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#615137} 10 December 2018, 16:43:37 UTC
9ed4d9b Blink WPT Bot 10 December 2018, 16:22:42 UTC [ChromeDriver] Make some mouse web platform tests work on wpt serve (#14304) I have changed ExecutePerformActions function in window_commands.cc to execute the actions input sent from Webdriver and convert an element in origin into coordinates. Bug: chromedriver:1897 Change-Id: I407dbad5e001f15ddd4edfd709f5460384e95530 Reviewed-on: https://chromium-review.googlesource.com/c/1356123 Reviewed-by: John Chen <johnchen@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#614838} 10 December 2018, 16:22:42 UTC
26390b3 Stephen McGruer 10 December 2018, 15:47:18 UTC [ScrollTimeline] Upstream writing-mode currentTime tests to WPT This CL upstreams the writing-mode related currentTime tests to WPT. There are a few mostly non-behavioral changes to the tests in this CL: * Some comments were edited for clarity. * For tests with more than one assert_equals(), descriptions were added to the asserts. This is to help locate failing assert_equal lines, as jsharness does not print out the line number of a failure. * In a few places we had more than one assert_equals for the same scenario (e.g. multiple cases where scroll was after the startScrollOffset point). These have been deduplicated. Bug: 911254 Change-Id: I5e814acea281e2587164de634da9a5415b53de2c Reviewed-on: https://chromium-review.googlesource.com/c/1366263 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#615126} 10 December 2018, 15:56:39 UTC
8832bcc Samuel Huang 10 December 2018, 15:11:30 UTC Revert "Create RTCDtlsTransport objects in the blink layer" This reverts commit d7d59c5b7e4110ba0a7c1752387fb1b5ea0282cb. Reason for revert: virtual/webrtc-wpt-unified-plan/external/wpt/webrtc/RTCRtpSender-transport.https.html fails in "WebKit Linux Trusty MSAN". Original change's description: > Create RTCDtlsTransport objects in the blink layer > > This CL does on-demand creation of blink-layer transport > objects. It also introduces a way to get at the webrtc::PeerConnection > object from the WebPeerConnectionHandler API. > > Bug: chromium:907849 > Change-Id: Ic86a5a66289c31d1f939a47d58bc194c32471cbd > Reviewed-on: https://chromium-review.googlesource.com/c/1358060 > Commit-Queue: Harald Alvestrand <hta@chromium.org> > Reviewed-by: Guido Urdaneta <guidou@chromium.org> > Reviewed-by: Henrik Boström <hbos@chromium.org> > Reviewed-by: Kentaro Hara <haraken@chromium.org> > Cr-Commit-Position: refs/heads/master@{#615072} TBR=hta@chromium.org,haraken@chromium.org,hbos@chromium.org,guidou@chromium.org Change-Id: Ie9c8d2e3dc5f97fc94ca5bf43cc30a9407d9fa4c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:907849 Reviewed-on: https://chromium-review.googlesource.com/c/1369719 Reviewed-by: Samuel Huang <huangs@chromium.org> Commit-Queue: Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#615115} 10 December 2018, 15:20:38 UTC
eedce7c Andrea Marchesini 28 November 2018, 18:46:20 UTC rel=noopener implicit for target=_blank in anchor and area elements when no rel attribute is set - WPT bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1503681 gecko-commit: 45e6f25036c57ad42140e749bb2927e5365d038c gecko-integration-branch: mozilla-inbound gecko-reviewers: annevk 10 December 2018, 14:10:48 UTC
94ac45d Philip Jägenstedt 23 November 2018, 09:20:10 UTC Reland "Find manifest for download by tags instead of commits" Reverted in https://github.com/web-platform-tests/wpt/pull/14208 as possible cause of https://github.com/web-platform-tests/wpt/issues/14207. This reverts commit 5438f72ea0bc2abb3754b2b906a34d497bd8457c. 10 December 2018, 13:56:29 UTC
18bb80e Dominic Farolino 10 December 2018, 13:24:44 UTC Add muted error tests for redirected scripts Helps with https://github.com/whatwg/fetch/issues/737. 10 December 2018, 13:24:44 UTC
b9825de youennf 10 December 2018, 13:23:37 UTC Treat more "no-cors" image loads as cross-origin In particular when it's redirected from same-origin to cross-origin to same-origin. Or cross-origin to same-origin. (Relative to the document responsible for the fetch.) 10 December 2018, 13:23:37 UTC
97a0309 Morten Stenshorne 10 December 2018, 11:42:28 UTC Don't estimate the top of bottom-aligned OOFs as bottom. (This is a reland of https://chromium-review.googlesource.com/c/chromium/src/+/1355920 with proper rebaselining) We'll incorrectly think that we get fragmented in that case, which will lead to incorrect height, which will lead to incorrect top offset, which will lead to incorrect fragmentation. This has probably been the cause for a flaky web test, that behaved even worse in LayoutNG, because in NG we force legacy layout as soon as fragmentation is involved (so when entering printing, we typically need to rebuild the entire layout object tree, with no former height to base the bottom estimate on (which is what saved us when NG is disabled - ehm, at least most of the time)). TBR=atotic@chromium.org,eae@chromium.org Bug: 910300 Change-Id: I00bce89900c50d6db9b39a4b72dbd6ab653184a7 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1365436 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#615089} 10 December 2018, 11:51:18 UTC
503a714 Robert Ma 05 December 2018, 21:08:52 UTC Use wpt run --affected on Taskcluster 10 December 2018, 10:13:21 UTC
837e5b7 Robert Ma 04 December 2018, 16:24:51 UTC Implement --affected as a flag of `wpt run` This is squashed and pulled from #14156 , with the unrelated changes removed (namely the Safari setup in .azure-pipelines.yml), and some review comments addressed. 10 December 2018, 10:13:21 UTC
acc3783 Harald Alvestrand 10 December 2018, 10:02:54 UTC Create RTCDtlsTransport objects in the blink layer This CL does on-demand creation of blink-layer transport objects. It also introduces a way to get at the webrtc::PeerConnection object from the WebPeerConnectionHandler API. Bug: chromium:907849 Change-Id: Ic86a5a66289c31d1f939a47d58bc194c32471cbd Reviewed-on: https://chromium-review.googlesource.com/c/1358060 Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#615072} 10 December 2018, 10:12:06 UTC
a4bbfb3 Lan Wei 10 December 2018, 10:10:17 UTC Make sure that Actions.perform is always passed a list (#14345) 10 December 2018, 10:10:17 UTC
a00b58d David Heiberg 04 December 2018, 16:14:52 UTC Updated hyper so that it uses the third_party/h2 instead of its own version of h2 10 December 2018, 10:02:54 UTC
9f2b713 qiuzhong 10 December 2018, 09:53:50 UTC Remove test-level assert property from tests (#14409) Test-level asserts is the only remaining use of is for test-level assert metadata. Remove all the assert property from tests and mark them as test comments if possible. For `help` and `author`, moving the information to the top of the test files. Fixes #14394. 10 December 2018, 09:53:50 UTC
226f3b5 Fergal Daly 10 December 2018, 04:05:41 UTC CSS: Migrate css-shadow-parts tests to wpt. The spec is now at first public working draft, so moving the forwarding tests under wpt/. Remove entire directory and references to it (the flag expectations file already skips everything in external, the tests are still skipped in their new location). Change-Id: I5ddaab9d7e956aa1624dfda531d8548640c7cee4 Reviewed-on: https://chromium-review.googlesource.com/c/1368858 Commit-Queue: Fergal Daly <fergal@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#615039} 10 December 2018, 04:14:04 UTC
8c0f2bd Zirro 10 December 2018, 03:49:52 UTC Add tests for clicking the child of a button element (#14426) 10 December 2018, 03:49:52 UTC
2d53857 Emilio Cobos Álvarez 07 December 2018, 22:54:03 UTC Fix / update tests. Differential Revision: https://phabricator.services.mozilla.com/D13550 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1511138 gecko-commit: 1879534289a4034a18002756d80cbf99f73d18da gecko-integration-branch: mozilla-inbound gecko-reviewers: smaug 09 December 2018, 21:53:28 UTC
86c56c1 George Roman 27 November 2018, 09:16:49 UTC Kill test processes whenever any error occurs 09 December 2018, 18:05:40 UTC
5349c6a autofoolip 08 December 2018, 07:32:28 UTC Update interfaces/webxr.idl (#14425) Source: https://github.com/tidoust/reffy-reports/blob/5aca30d/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/465263946 08 December 2018, 07:32:28 UTC
ed68c26 James Graham 06 December 2018, 17:03:42 UTC Add an infrastructure/ test to demonstrate file upload 08 December 2018, 03:57:30 UTC
cb2ee82 James Graham 06 December 2018, 17:03:06 UTC Add a wptserve substitution to get a path relative to the current document This is helpful for constructing file:// URLs and for uploading files 08 December 2018, 03:57:30 UTC
ba8f073 James Graham 06 December 2018, 17:02:05 UTC Ensure that file uploads work in Firefox Without this pref set, the marionette file upload codepath doesn't work. 08 December 2018, 03:57:30 UTC
6087baf Nicolas Pena 07 December 2018, 22:41:47 UTC Fix secureConnectionStart when connection is reused Per ResourceTiming spec, if a connection is reused then secureConnectionStart must return fetchStart, not 0. Bug: 404501 Change-Id: Ica208c98cfea0afa9dd22e4edc83cc3c430c219f Reviewed-on: https://chromium-review.googlesource.com/c/1363906 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/master@{#614849} 07 December 2018, 22:50:53 UTC
b513fa9 Brian Birtles 07 December 2018, 01:19:22 UTC Add tests for filling effects Differential Revision: https://phabricator.services.mozilla.com/D13932 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1488122 gecko-commit: 872ccfbcfe6f7abab6aa425f00d28188d0b8cbc5 gecko-integration-branch: autoland gecko-reviewers: hiro 07 December 2018, 21:15:30 UTC
6a51887 autofoolip 07 December 2018, 10:59:06 UTC Update interfaces/webrtc.idl (#14412) Source: https://github.com/tidoust/reffy-reports/blob/5608118/whatwg/idl/webrtc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/464817407 07 December 2018, 10:59:06 UTC
3460c9c James Graham 04 December 2018, 22:46:04 UTC Fix logging setup for ./mach wpt --product When running non-Firefox products in wpt we go through the run.py script from upstream. Therefore we need to initialise the logger in that module as well as the one in wptrunner now that it's been properly converted to use logging rather than print statements. In addition, we change the run.py module to allow passing in logging defaults for the case where nothing is specified on the command line since the behaviour for wpt upstream is different to the behaviour for gecko. Differential Revision: https://phabricator.services.mozilla.com/D13547 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1511335 gecko-commit: bf12a43a4100cc07d31447e4b148a7f27af5e6e2 gecko-integration-branch: autoland gecko-reviewers: ahal 07 December 2018, 09:42:18 UTC
388f93a Sven Sauleau 06 December 2018, 13:54:49 UTC Remove stray property from memory/constructor.any.js. It was copied from the WebAssembly.Table tests. 07 December 2018, 08:33:41 UTC
5608dc9 Hiroki Nakagawa 07 December 2018, 06:37:54 UTC Worklet: Use <meta name="timeout"> instead of SlowTests annotations for slow WPTs <meta name="timeout"> is prefereable for WPTs: https://web-platform-tests.org/writing-tests/testharness-api.html#harness-timeout Bug: 912240 Change-Id: I3c4a9acb1fb070c34d10f59ff9d3fd3d2bd11afb Reviewed-on: https://chromium-review.googlesource.com/c/1366469 Reviewed-by: Matt Falkenhagen <falken@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#614626} 07 December 2018, 06:45:59 UTC
2d0f68b Daniel Murphy 07 December 2018, 01:04:51 UTC [IndexedDB] Testing ordering and error handling for transaction.commit * Tests that transaction ordering is consistent, even if a transaction calls commit(). * Tests that request errors cause a commit()-ed transaction to abort. The second case seems to be broken in our implementation. R=andreasbutler@google.com, cmp@chromium.org Bug: 911877 Change-Id: I47da6ce9d350f6c47afcd02cf808d4fefb5f013f Reviewed-on: https://chromium-review.googlesource.com/c/1362477 Commit-Queue: Daniel Murphy <dmurph@chromium.org> Reviewed-by: Chase Phillips <cmp@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#614512} 07 December 2018, 01:17:57 UTC
008bfc9 Stephen McGruer 07 December 2018, 01:04:42 UTC [ScrollTimeline] Upstream based currentTime tests to WPT This CL starts to upstream the currentTime tests to WPT. To split this up, we start with just the 'basic' tests - basic functionality, adjusting for time range, and start/end scroll offsets. The writing mode and NaN tests will follow in later patches. There are a few mostly non-behavioral changes to the tests in this CL: * Some comments were edited for clarity. * For tests with more than one assert_equals(), descriptions were added to the asserts. This is to help locate failing assert_equal lines, as jsharness does not print out the line number of a failure. * In a few places we had more than one assert_equals for the same scenario (e.g. multiple cases where scroll was after the startScrollOffset point). These have been deduplicated. Bug: 911254 Change-Id: I783fcf7f43cda876defa9c36db9a0e7dff4e82c7 Reviewed-on: https://chromium-review.googlesource.com/c/1366297 Reviewed-by: Yi Gu <yigu@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#614510} 07 December 2018, 01:13:26 UTC
ffcb833 Andrew Comminos 06 December 2018, 19:50:34 UTC Check the source browsing context's CSP in Location::SetLocation prior to dispatching a navigation to a `javascript:` URL. Makes `javascript:` navigations via window.location.href compliant with https://html.spec.whatwg.org/#navigate, which states that the source browsing context must be checked (rather than the current browsing context). Bug: 909865 Change-Id: Id6aef6eef56865e164816c67eb9fe07ea1cb1b4e Reviewed-on: https://chromium-review.googlesource.com/c/1359823 Reviewed-by: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andrew Comminos <acomminos@fb.com> Cr-Commit-Position: refs/heads/master@{#614451} 06 December 2018, 19:57:02 UTC
047734d Ian Kilpatrick 06 December 2018, 18:50:14 UTC [LayoutNG] Simplify & correct static position for OOF positioned. This patch is primarily simplifies how we determine the static position for an OOF positioned node, within the inline context. There are many fixes, (see test cases). Additionally, fixed positioned nodes, now work when they have an inline level containing block. Bug: 636993 Change-Id: I36b573578fc85d9ba9b757f258ec7391eec73c0a Reviewed-on: https://chromium-review.googlesource.com/c/1356999 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#614426} 06 December 2018, 19:04:05 UTC
fc87d9b Robert Ma 05 December 2018, 22:52:30 UTC Run affected tests on Taskcluster without changes One step towards https://github.com/web-platform-tests/wpt.fyi/issues/708 06 December 2018, 18:18:33 UTC
9a3c69f Mason Freed 06 December 2018, 16:52:33 UTC Implement correct opacity and filter handling within backdrop-filter Prior to this CL, opacity and filters applied to the backdrop-filtered element did not get applied to the backdrop-filtered backdrop. Now, the opacity and filters get applied directly to the backdrop-filtered image directly, which is an approximation but should be very close. Also fixed up a few of the backdrop-filter tests to account for this, and removed a few lines from TestExpectations that now work. Bug: 497522, 524689 Change-Id: If671bdf65ac0ae04cf175143eb8949ff4be0837b Reviewed-on: https://chromium-review.googlesource.com/c/1357626 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#614383} 06 December 2018, 17:01:07 UTC
692ce5a youennf 06 December 2018, 15:51:46 UTC Move addStream test to webrtc/legacy (#14044) * Move addStream test to webrtc/legacy * Migrating existing stat test from addStream to addTrack 06 December 2018, 15:51:46 UTC
6185fc0 qiuzhong 06 December 2018, 12:52:21 UTC Remove support for the timeout from testharness.js (#14309) Fixes https://github.com/web-platform-tests/wpt/issues/11120. 06 December 2018, 12:52:21 UTC
3417cb3 Alicia Boya García 06 December 2018, 10:58:26 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=189727 06 December 2018, 11:10:34 UTC
168da20 Kent Tamura 06 December 2018, 10:15:28 UTC Rename MojoLayoutTestHelper to MojoWebTestHelper mojo_layouttest_test.mojom is renamed to mojo_web_test_helper_test.mojom. It keeps _test suffix indicating it affects only tests. Bug: 843412 Change-Id: Iddfdfcbfd87228fb9ee8abd2777f4838c4b66801 Reviewed-on: https://chromium-review.googlesource.com/c/1362717 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#614302} 06 December 2018, 10:24:30 UTC
93af5d9 autofoolip 06 December 2018, 09:17:28 UTC Update interfaces/web-nfc.idl (#14388) Source: https://github.com/tidoust/reffy-reports/blob/1c79dd7/whatwg/idl/web-nfc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/464203271 06 December 2018, 09:17:28 UTC
4bdeca6 Philip Jägenstedt 06 December 2018, 09:13:53 UTC Tests for SVG tabindex/focus/blur (#10149) * Add test for SVG focus flag * Update focus-flag test * Add test for default tabIndex value Adapted from html/editing/focus/sequential-focus-navigation-and-the-tabindex-attribute/focus-tabindex-default-value.html * Add focus management test Adapted from HTML version at /html/editing/focus/focus-management/focus-events.html * Add focus composed test Based on HTML's composed.window.js * Respond to feedback Remove test for audio/video without controls and add non root svg 06 December 2018, 09:13:53 UTC
0d02fc9 Frédéric Wang 05 December 2018, 15:50:09 UTC Add link to CSS Overscroll behavior spec. 06 December 2018, 09:12:20 UTC
6608f66 Frédéric Wang 05 December 2018, 11:28:05 UTC Move overscrollBehavior-manual.html into css/css-overscroll-behavior This property does not belong to the CSSOM View spec. 06 December 2018, 09:12:20 UTC
0347da3 autofoolip 06 December 2018, 08:56:39 UTC Update interfaces/event-timing.idl (#14387) Source: https://github.com/tidoust/reffy-reports/blob/1c79dd7/whatwg/idl/event-timing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/464203271 06 December 2018, 08:56:39 UTC
3e60f8f Matt Falkenhagen 06 December 2018, 05:42:55 UTC WPT: service worker: fix test for CSS base URL. The existing test was asserting the opposite of the standard, which is to use the response URL. See https://github.com/whatwg/fetch/pull/146. This CL does the following: - Tests that a CSS stylesheet fetched via respondWith(fetch(responseUrl) uses responseUrl as its base URL. - Tests that a CSS stylesheet fetched via respondWith(new Response()) uses the response URL (which is the request URL) as its base URL. - Changes the test to not test cross-origin stylesheets. That is more complex than needed for this test, and there is talk of making subresource requests from opaque stylesheets skip the service worker, which would render the test ineffective for testing base URL. - Changes the test to use waitUntil() in the message event to try to ensure the service worker stays alive between the message and fetch events. Bug: 911974 Change-Id: I167dfe86986ec718a50d512f862f1eb49889608b Reviewed-on: https://chromium-review.googlesource.com/c/1362776 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Ben Kelly <wanderview@chromium.org> Cr-Commit-Position: refs/heads/master@{#614277} 06 December 2018, 05:52:00 UTC
ee3ec2e Tim Haloun 06 December 2018, 01:56:20 UTC web platform tests for new networkPriority encoding parameter. Bug: webrtc:5008 Change-Id: I867b0811917f0356f05417f6186124d92c3a0622 Reviewed-on: https://chromium-review.googlesource.com/c/1357515 Commit-Queue: Tim Haloun <thaloun@chromium.org> Reviewed-by: Florent Castelli <orphis@chromium.org> Cr-Commit-Position: refs/heads/master@{#614228} 06 December 2018, 02:05:12 UTC
093a97b Koji Ishii 05 December 2018, 22:23:08 UTC [LayoutNG] Fix when `break-word` is applied to inline boxes This patch fixes NGLineBreaker when `break-word` is applied to inlne boxes. It works properly only when `break-word` is applied to containing block before this fix. To fix this, NGInlineItemResult keeps the value of `break_anywhere_if_overflow` for each item. Change-Id: I6e51ffa31a015f0e2ba82f536982a912424b9eba Bug: 902659 Reviewed-on: https://chromium-review.googlesource.com/c/1355310 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#614125} 05 December 2018, 22:32:04 UTC
796c622 youennf 05 December 2018, 21:10:34 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=189727 (#14369) 05 December 2018, 21:10:34 UTC
5781139 Eric Willigers 05 December 2018, 20:06:21 UTC SVG Painting: computed property values (#14211) * SVG Painting: computed property values Keyword values are as specified. Lengths are converted to absolute lengths. Urls are converted to absolute paths. Found bug: https://bugs.chromium.org/p/chromium/issues/detail?id=908058 *-opacity should be clamped to [0,1] 05 December 2018, 20:06:21 UTC
8dacc52 Eric Willigers 05 December 2018, 20:02:48 UTC SVG property parsing with CSS length units (#14367) Test all the length units defined in CSS Values and Units Module Level 3 https://www.w3.org/TR/css-values-3/#lengths are parsed successfully in SVG properties. 05 December 2018, 20:02:48 UTC
31e51c5 Roger McFarlane 05 December 2018, 18:10:58 UTC [Sheriff] Revert "Don't estimate the top of bottom-aligned OOFs as bottom." This reverts commit d5096cb8a5d544acb51f8b4df908775b6584778f. Reason for revert: This looks like a likely culprit breaking WebKit Win10 printing/absolute-position-headers-and-footers.html virtual/threaded/printing/absolute-position-headers-and-footers.html https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/WebKit%20Win10 Original change's description: > Don't estimate the top of bottom-aligned OOFs as bottom. > > We'll incorrectly think that we get fragmented in that case, which will > lead to incorrect height, which will lead to incorrect top offset, > which will lead to incorrect fragmentation. > > This has probably been the cause for a flaky web test, that behaved > even worse in LayoutNG, because in NG we force legacy layout as soon as > fragmentation is involved (so when entering printing, we typically need > to rebuild the entire layout object tree, with no former height to base > the bottom estimate on (which is what saved us when NG is disabled - > ehm, at least most of the time)). > > Bug: 910300 > Change-Id: I8e152f77e9a94bb05e51f02a24be6ef5fe03c6f9 > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng > Reviewed-on: https://chromium-review.googlesource.com/c/1355920 > Reviewed-by: Aleks Totic <atotic@chromium.org> > Commit-Queue: Morten Stenshorne <mstensho@chromium.org> > Cr-Commit-Position: refs/heads/master@{#613930} TBR=eae@chromium.org,atotic@chromium.org,mstensho@chromium.org Change-Id: I5949a6a6e0b9e5cfa281b7abcd266ad63f7af85f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 910300 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1363646 Reviewed-by: Roger McFarlane <rogerm@chromium.org> Commit-Queue: Roger McFarlane <rogerm@chromium.org> Cr-Commit-Position: refs/heads/master@{#614025} 05 December 2018, 18:19:34 UTC
d59c66c Nicolas Pena 05 December 2018, 15:33:57 UTC Reland "[EventTiming] Always buffer firstInput" This is a reland of b6e2cb9b364649724a1577b0c842074e12b82f27 Flaky tests are fixed: the assumption that wait is sufficient to expect input events to be processed is false. Original change's description: > [EventTiming] Always buffer firstInput > > Before, we'd buffer the firstInput entry only if it happened before > onload. This CL forces firstInput to always be buffered. This means > EventTiming code is called more in some tests, so the event hardware > timestamp is no longer guaranteed to be nonzero, and a couple of xr > tests require double RAF to avoid competing with the swap promises from > Event Timing. > > Bug: 841224, 843184 > > Change-Id: I942b934c387798c100da4ecfff52affb66ab94e8 > Reviewed-on: https://chromium-review.googlesource.com/c/1355880 > Reviewed-by: Timothy Dresser <tdresser@chromium.org> > Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> > Cr-Commit-Position: refs/heads/master@{#612703} Bug: 823744, 843184 Change-Id: I5286f3748d35c0c9d5972d301cd5abcf6e453da4 Reviewed-on: https://chromium-review.googlesource.com/c/1358910 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#613973} 05 December 2018, 15:42:04 UTC
2d66758 Philip Jägenstedt 05 December 2018, 15:07:28 UTC Merge remote-tracking branch 'origin/master' into HEAD 05 December 2018, 15:07:28 UTC
9a3a9e1 Luke Bjerring 05 December 2018, 14:55:42 UTC Add performance object 05 December 2018, 15:01:24 UTC
c539843 Luke Bjerring 05 December 2018, 14:54:06 UTC Add idlharness test 05 December 2018, 15:01:24 UTC
6b4c63e Automat af Gränssnitt 05 December 2018, 13:30:37 UTC Add interfaces/event-timing.idl Source: https://github.com/tidoust/reffy-reports/blob/9dd0ab0/whatwg/idl/event-timing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463841803 05 December 2018, 15:01:24 UTC
3f5d8af jugglinmike 05 December 2018, 14:59:26 UTC [wptrunner] Support any Sauce Connect argument (#14356) Implement the command-line argument `--sauce-connect-arg` as a pass-through to the Sauce Connect binary. This gives users more control over the way the binary is configured which is particularly important in combination with the existing `--sauce-connect-binary` argument (since the list of available arguments is subject to change between releases). 05 December 2018, 14:59:26 UTC
54e379b L. David Baron 05 December 2018, 14:07:23 UTC Sync Mozilla CSS tests as of https://hg.mozilla.org/mozilla-central/rev/caae48e4e6cf4477e11b6464bccdd5ba679ae31a . (#14375) This contains changes from [bug 1511963](https://bugzilla.mozilla.org/show_bug.cgi?id=1511963) by @mrego, reviewed by @emilio. 05 December 2018, 14:07:23 UTC
290b849 Daniel Vogelheim 05 December 2018, 11:32:22 UTC [Trusted Types] Tests from WICG GitHub ported to WPT WICG GitHub = https://github.com/WICG/trusted-types/tree/master/tests ported Bug: 739170 Change-Id: I56563c16facd7c17d79e7b5625115a0f045618f8 Reviewed-on: https://chromium-review.googlesource.com/c/1209708 Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613937} 05 December 2018, 11:40:16 UTC
9f57a56 autofoolip 05 December 2018, 10:55:43 UTC Update interfaces/webxr.idl (#14372) Source: https://github.com/tidoust/reffy-reports/blob/81fd807/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463710129 05 December 2018, 10:55:43 UTC
e298bbf autofoolip 05 December 2018, 10:53:37 UTC Update interfaces/web-nfc.idl (#14371) Source: https://github.com/tidoust/reffy-reports/blob/81fd807/whatwg/idl/web-nfc.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463710129 05 December 2018, 10:53:37 UTC
66004f5 Morten Stenshorne 05 December 2018, 10:40:34 UTC Don't estimate the top of bottom-aligned OOFs as bottom. We'll incorrectly think that we get fragmented in that case, which will lead to incorrect height, which will lead to incorrect top offset, which will lead to incorrect fragmentation. This has probably been the cause for a flaky web test, that behaved even worse in LayoutNG, because in NG we force legacy layout as soon as fragmentation is involved (so when entering printing, we typically need to rebuild the entire layout object tree, with no former height to base the bottom estimate on (which is what saved us when NG is disabled - ehm, at least most of the time)). Bug: 910300 Change-Id: I8e152f77e9a94bb05e51f02a24be6ef5fe03c6f9 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/c/1355920 Reviewed-by: Aleks Totic <atotic@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#613930} 05 December 2018, 10:48:15 UTC
f4449f8 jgraham 30 November 2018, 18:42:24 UTC Update wptrunner.py 05 December 2018, 10:26:50 UTC
ff755aa Wes Kocher 29 November 2018, 23:51:21 UTC Make sure --repeat-until-unexpected doesn't loop over zero tests If zero tests are selected to run while --repeat-until-unexpected is specified, wptrunner can get into a fast infinite loop of running nothing until killed by the user. This patch should stop that from happening by breaking the loop after the first iteration of nothing finishes. Differential Revision: https://phabricator.services.mozilla.com/D13204 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1504357 gecko-commit: f988af9437f591cc5c7d3917ba370e2edc82d1a6 gecko-integration-branch: central gecko-reviewers: jgraham 05 December 2018, 10:26:50 UTC
30b3f1d Morten Stenshorne 05 December 2018, 06:59:11 UTC [LayoutNG] Honor {min,max}-inline-size when using cached intrinsic size. We store cached min/max intrinsic inline sizes in legacy layout objects. These are normally constrained against {min,max}-inline-size, but not if those values are percentage based, since percentages are obviously not resolvable at the time of calculating intrinsic sizes. In such cases we cannot use the cached values directly. Calculate intrinsic size and apply constraints on our own in such cases. Bug: 900390 Change-Id: I90b8ab590fa97e8ec7929bc1af38cf3824f9ea6b Reviewed-on: https://chromium-review.googlesource.com/c/1360853 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#613889} 05 December 2018, 07:07:33 UTC
aaa8f82 Florian Rivoal 05 December 2018, 03:58:14 UTC Merge pull request #14368 from MurakamiShinyu/overflow-wrap [css-text] line-height fix on overflow-wrap-break-word-004 and -005 05 December 2018, 03:58:14 UTC
9ccd954 MurakamiShinyu 05 December 2018, 03:31:07 UTC [css-text] line-height fix on overflow-wrap-break-word-004 and -005 tests - `line-height: 1em` was specified on the `.test {...}` but not on the `.red` and `.fail` blocks. As a result, the line-height of the `.red` and `.fail` blocks depended on the browser, and the red color appeared on Firefox. 05 December 2018, 03:31:07 UTC
c4eb7b7 Jarryd 05 December 2018, 02:13:04 UTC Refactor storage estimate wpt to use async/await. Change-Id: Iec6ddc03ce5a813f219273e4a8a7d5098b3fb936 Reviewed-on: https://chromium-review.googlesource.com/c/1318739 Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#613817} 05 December 2018, 02:21:43 UTC
c05265a Kai Ninomiya 05 December 2018, 01:54:09 UTC testharness.md: Remove errant spaces in file paths Removes spaces in /common /subset-tests.js /common/subset-tests-by- key.js 05 December 2018, 02:03:11 UTC
614fd87 MurakamiShinyu 03 December 2018, 07:02:47 UTC [css-text] Update 'line-break' tests ### Fix test file name numbering The problem was that `line-break-normal-*` and `line-break-strict-*` had diffrent numbering for same ranges, e.g. `line-break-normal-021` and `line-break-strict-014` for same iteration marks. It was confusing, so I changed the numbering for 'normal' to be the same as for 'strict'. - line-break-normal-021 → line-break-normal-014 - line-break-normal-022 → line-break-normal-015 - line-break-normal-023a → line-break-normal-016a - line-break-normal-023b → line-break-normal-016b - line-break-normal-024a → line-break-normal-017a - line-break-normal-024b → line-break-normal-017b ### Fix tests for Inseparatable characters The tests for Inseparatable characters `line-break-strict-015` and `line-break-normal-015` (was `line-break-normal-022`) had wrong assertion "does not allow line breaking **before** inseparable characters". This should be "does not allow line breaking **between** inseparable characters". I changed the tests to test line breaking **between** (not **before**) two inseparable characters. ### Fix tests for Centered punctuation marks The tests for Centered punctuation marks `line-break-strict-016a` and `line-break-normal-016a` (was `line-break-normal-023a`) contained tests for EAW=Narrow characters (U+003A, U+003B, U+0021, U+003F) that are excluded in the current 'line-break' spec. ### Fix tests for Postfixes The tests for Postfixes `line-break-strict-017a` and `line-break-normal-017a` (was `line-break-normal-024a`) contained tests for EAW=Narrow characters (U+0025 and U+00A2) that are excluded in the current 'line-break' spec. ### Add tests for Prefixes Added the tests for line breaking after Prefixes `line-break-*-018`. ### Add 'loose' and 'normal' values tests that were missing - line-break-loose-011 .. line-break-loose-017b - line-break-normal-011 .. line-break-normal-013 ### Adjust width of the test block I changed the width of the test block `p.test, p.control {...}` that was `width: 10em` to `width: 10.2em`. This extra (.2em) width is needed to prevent unexpected line breaking caused by some symbol characters wider than 1em. I found this problem with `line-break-loose-018`. The width of U+2116 "№" is slightly wider than 1em and if the block width is 10em the line breaking occurs before that character, and the test always fails. 04 December 2018, 23:16:38 UTC
3960fff MurakamiShinyu 04 December 2018, 15:49:56 UTC [css-text] Some fixes on 'word-break-break-all-*' tests ### word-break-break-all-010 and word-break-break-all-011 - `line-height: 1em` was specified on the `.test {...}` but not on the `.red {...}`. As a result, the line-height of the `.red` block depended on the browser, and the red color appeared on Firefox. ### word-break-break-all-020 Fix erros (typo?) - `div::nth-of-type` → `div:nth-of-type` - `break-word` → `break-all` 04 December 2018, 23:14:56 UTC
164bf82 Stephen McGruer 04 December 2018, 20:12:36 UTC [ScrollTimeline] Begin upstreaming tests to WPT This CL uploads some basic construction tests for ScrollTimeline. Since the Chrome implementation still requires timeRange, it is left in for now (but documented!). Spec: https://wicg.github.io/scroll-animations Bug: 911254 Change-Id: Ia7da845eddcd27ea6e7d3fbaf3a008cbdf6d149a Reviewed-on: https://chromium-review.googlesource.com/c/1354222 Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#613666} 04 December 2018, 20:20:41 UTC
1f9bc10 Daniel Vogelheim 04 December 2018, 14:19:21 UTC WorkerGlobalScope::importScripts() modified to accept TrustedTypes Existing implementation made private and renamed importScriptsFromString. New version wraps importScriptsFromString. Service_Worker_Global_Scope::importScripts() signature adjusted to accept TrustedTypes. Bug: 739170 Change-Id: Ifa7d9e9f13f0903ecdf0b4c1553f6039141b9b76 Reviewed-on: https://chromium-review.googlesource.com/c/1144825 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#613538} 04 December 2018, 14:27:30 UTC
4a0a94b Andy Paicu 04 December 2018, 12:32:37 UTC Rework of "inherit the navigation initiator when navigating" Spec: https://w3c.github.io/webappsec-csp/#initialize-document-csp This is a rework and reland of https://chromium-review.googlesource.com/c/chromium/src/+/1314633 The initial patch got reverted because it did not pass the trusty leak build checks. The issue was that holding to the initiator document as a member in FrameLoader was holding said document alive unreasonably long. Instead this rework holds a copy of the initiator's CSP. Bug: 905301, 894228, 836148 Change-Id: Ic12c28d20c53def5d6753449c3c4da7de5242ca2 Reviewed-on: https://chromium-review.googlesource.com/c/1353978 Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#613521} 04 December 2018, 12:54:43 UTC
0b2da26 Andy Paicu 04 December 2018, 12:23:51 UTC Fixes to the plugin-types csp checks and added empty directive check Fixed the external/wpt/content-security-policyplugin-types tests as the current ones are actually entirely useless as they pretty much always pass. Discovered and raised crbug.com/911114, also skipping the (now correct) tests that uncovered this issue. Added new test for empty plugin-types directive blocking every plugin. Removed tests in http/tests/security/contentSecurityPolicy that are direct 1-to-1 equivalents of these tests. Spec: https://github.com/w3c/webappsec-csp/pull/374 Bug: 694525 Change-Id: I91a548c6035a82310be077501934a51cf85525a2 Reviewed-on: https://chromium-review.googlesource.com/c/1358457 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613517} 04 December 2018, 12:50:46 UTC
a374387 jgraham 04 December 2018, 11:27:56 UTC Update fennec.py 04 December 2018, 11:50:58 UTC
b7ec9ec James Graham 01 December 2018, 00:35:02 UTC Fixup shutting down fennec Remove the desktop-only shutdown code and ensure that the app isn't running before the tests start, since we can't have multiple copies of the same app running at a time. Depends on D13088 Differential Revision: https://phabricator.services.mozilla.com/D13089 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1510258 gecko-commit: 7d17aa7e056119b29b713caa1bd63d575ad2cc56 gecko-integration-branch: autoland gecko-reviewers: gbrown 04 December 2018, 11:50:58 UTC
6111e21 Ms2ger 30 November 2018, 16:38:11 UTC Fix path argument to wpt lint. 04 December 2018, 11:26:39 UTC
fc6921b Andy Paicu 04 December 2018, 11:03:53 UTC Inherit the self source when we inherit the policy Spec: https://w3c.github.io/webappsec-csp/#initialize-document-csp Bug: 910841 Change-Id: Ic06cf87577c46cfc3a8a2581160c32e22f3956e8 Reviewed-on: https://chromium-review.googlesource.com/c/1357084 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#613501} 04 December 2018, 11:11:41 UTC
0dcde64 autofoolip 04 December 2018, 10:51:41 UTC Update interfaces/audio-output.idl (#14069) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/audio-output.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:51:41 UTC
3590884 autofoolip 04 December 2018, 10:50:10 UTC Update interfaces/mediacapture-streams.idl (#13999) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/mediacapture-streams.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:50:10 UTC
e2e3234 autofoolip 04 December 2018, 10:42:43 UTC Update interfaces/payment-method-basic-card.idl (#14070) Source: https://github.com/tidoust/reffy-reports/blob/a74aa91/whatwg/idl/payment-method-basic-card.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/455362278 04 December 2018, 10:42:43 UTC
64a4678 autofoolip 04 December 2018, 10:41:44 UTC Update interfaces/performance-timeline.idl (#14276) Source: https://github.com/tidoust/reffy-reports/blob/6f59720/whatwg/idl/performance-timeline.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/460633569 04 December 2018, 10:41:44 UTC
51acb5a autofoolip 04 December 2018, 10:41:09 UTC Update interfaces/input-events.idl (#14351) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/input-events.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:41:09 UTC
8a1654e autofoolip 04 December 2018, 10:39:38 UTC Update interfaces/credential-management.idl (#14350) Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/credential-management.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 10:39:37 UTC
9093fde Automat af Gränssnitt 04 December 2018, 07:11:18 UTC Update interfaces/DOM-Parsing.idl Source: https://github.com/tidoust/reffy-reports/blob/3f10965/whatwg/idl/DOM-Parsing.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/463186803 04 December 2018, 09:42:05 UTC
774f67d Gyuyoung Kim 04 December 2018, 05:19:55 UTC [USVString] Add a rough test case for navigator.unregisterProtocolHandler Although r525634 updated the URL type of registerProtocolHandler from DOMString to USVString, it didn't add a test case because it was a bit complex. And also, issue 933668 added the rough test for navigator.registerProtocolHandler. But, it didn't add a test for the navigator.unregisterProtocolHandler. So this CL adds a rough test case for navigator.unregisterProtocolHandler. Bug: 790860 Change-Id: Ib54c058e4c61db59b73486d28fbd3db5bfdd36c7 Reviewed-on: https://chromium-review.googlesource.com/c/1359976 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Cr-Commit-Position: refs/heads/master@{#613425} 04 December 2018, 05:28:21 UTC
1abcb70 jugglinmike 04 December 2018, 00:24:59 UTC [service-workers] Use asynchronous cleanup (#13164) 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]. Use that 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 04 December 2018, 00:24:59 UTC
ef72a20 Philip Jägenstedt 03 December 2018, 22:49:50 UTC Rename audio-output idlharness test for secure context change (#14337) Needed for https://github.com/web-platform-tests/wpt/pull/14069. 03 December 2018, 22:49:50 UTC
a0aee6e Kevin Ellis 03 December 2018, 19:30:25 UTC Simplify interpolation of 2-D matrix transforms. The decomposition of a transformation matrix into translations, rotation, scale and skew transforms is not unique. In some cases, the generalized 3-D decomposition does not align with the working draft for CSS transforms (https://drafts.csswg.org/css-transforms/). In the special case where the transforms being interpolated are both 2-D, a simplified model provides more restricted set of decomposition transforms with less computational overhead. Bug: 797472 Change-Id: I2b8ba99fe02c2eef878d94f5dfaea55c39652759 Reviewed-on: https://chromium-review.googlesource.com/c/1332253 Commit-Queue: Kevin Ellis <kevers@chromium.org> Commit-Queue: Ian Vollick <vollick@chromium.org> Reviewed-by: Ian Vollick <vollick@chromium.org> Cr-Commit-Position: refs/heads/master@{#613191} 03 December 2018, 19:38:11 UTC
7de8ae3 James Graham 30 November 2018, 18:21:30 UTC Update the docker image 03 December 2018, 18:54:19 UTC
3c36672 James Graham 30 November 2018, 18:21:08 UTC Fetch tags on initial clone This is slow, but means we have the information needed to download the manifest 03 December 2018, 18:54:19 UTC
dedf235 James Graham 30 November 2018, 18:20:03 UTC Move most of start.sh to outside the Docker image This reduces the number of changes that require a rebuild of the docker image. 03 December 2018, 18:54:19 UTC
073eaac Mugdha Lakhani 03 December 2018, 14:41:26 UTC [Background Fetch] Remove records_ from BackgroundFetchRegistration. This had been introduced to simplify access to active fetches, but has the following issues: 1. It makes match() and matchAll() inconsistent with Cache API's match() and matchAll(), which return new independently-consumable response(s) every time they're called. 2. It breaks retries for responses, when downloading from a server that doesn't support resuming of downloads. For details, see https://docs.google.com/document/d/1CrbWrnnshhyp_SfiAeuODpnQX36GK3Bsi19rXQGez6Q/edit?usp=sharing The CL also updates the WPT test accordingly. Bug: 875201 Change-Id: I2c33717cbee36f0d707e814506c0bae9b5a4f31f Reviewed-on: https://chromium-review.googlesource.com/c/1355121 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#613079} 03 December 2018, 14:50:54 UTC
back to top