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
ecc1a8f Anne van Kesteren 17 February 2017, 10:44:29 UTC WIP test for document.domain 07 June 2018, 14:19:25 UTC
dd8e0ac Servo WPT Sync 07 June 2018, 13:02:26 UTC Merge pull request #11412 from web-platform-tests/sync_320e4fd58a3bd93b844d9596e72027d5f3781f3d Merge pull request #11412 from sync_320e4fd58a3bd93b844d9596e72027d5f3781f3d 07 June 2018, 13:02:26 UTC
ce1a1d3 Servo WPT Sync 07 June 2018, 13:02:13 UTC Merge pull request #11411 from web-platform-tests/sync_90693712e87eed75ff61cb67176cff92b514985c Merge pull request #11411 from sync_90693712e87eed75ff61cb67176cff92b514985c 07 June 2018, 13:02:13 UTC
8670bf3 Servo WPT Sync 07 June 2018, 13:01:56 UTC Merge pull request #11410 from web-platform-tests/sync_54ad86342ade28ef425cfb50a2e502170e844198 Merge pull request #11410 from sync_54ad86342ade28ef425cfb50a2e502170e844198 07 June 2018, 13:01:56 UTC
1bb7f08 Servo WPT Sync 07 June 2018, 13:01:41 UTC Merge pull request #11409 from web-platform-tests/sync_d0e05e0d4283f03892b688225b0134a1b6af84e2 Merge pull request #11409 from sync_d0e05e0d4283f03892b688225b0134a1b6af84e2 07 June 2018, 13:01:41 UTC
320e4fd Jonas Reinwald 07 June 2018, 13:01:31 UTC Implement read methods on FileReaderSync Upstreamed from https://github.com/servo/servo/pull/19511 [ci skip] 07 June 2018, 13:01:33 UTC
54ad863 tigercosmos 07 June 2018, 13:01:30 UTC move to wpt Upstreamed from https://github.com/servo/servo/pull/20858 [ci skip] 07 June 2018, 13:01:33 UTC
9069371 Gregory Terzian 07 June 2018, 13:01:31 UTC improve spec compliance of window.close Upstreamed from https://github.com/servo/servo/pull/20865 [ci skip] 07 June 2018, 13:01:33 UTC
d0e05e0 Gregory Terzian 07 June 2018, 13:01:30 UTC prevent overwriting of salvageable state in later prompt/unload steps Upstreamed from https://github.com/servo/servo/pull/20837 [ci skip] 07 June 2018, 13:01:33 UTC
bc87c81 Morten Stenshorne 07 June 2018, 08:57:58 UTC Correctly detect when a multicol descendant becomes or ceases to be a containing block. When a descendant of a multicol container becomes a containing block for out-of-flow positioned objects, or ceases to be one, out-of-flow positioned children may become or cease to be a part of the fragmentation context. We didn't detect this correctly. We only checked for transforms (in addition to position:relative). Make sure we check for filters too, now that those also establish containing blocks. Bug: 847328 Change-Id: I7ab47860bb8d9f8d9b0256b25e1123c34f73e8f4 Reviewed-on: https://chromium-review.googlesource.com/1089336 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#565210} 07 June 2018, 12:46:59 UTC
005c381 Matt Falkenhagen 07 June 2018, 08:30:04 UTC service worker: Add test for CSS cross-origin access. Tests for https://chromium-review.googlesource.com/c/chromium/src/+/1088335 Bug: 848786 Change-Id: I39d71d9aa2d1c0522c7a386405128297f62a0b24 Reviewed-on: https://chromium-review.googlesource.com/1088719 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#565208} 07 June 2018, 12:38:45 UTC
81303e1 Philip Jägenstedt 07 June 2018, 12:22:39 UTC HTML: update hashchange/popstate event tests For https://github.com/whatwg/html/pull/3737. 07 June 2018, 12:22:39 UTC
a7853ac Emilio Cobos Álvarez 06 June 2018, 09:49:01 UTC Ensure <slot> disables whitespace optimizations. The whitespace optimization code only knows about the light tree. It's not a great idea to try to put flattened tree children of a slot through there, since the children may not be assigned to the same slot, or to any slot (in which case we crash). We should probably rename XBLInvolved to ShadowDOMOrXBLInvolved too, I guess. Note that the ShadowRoot case already sets the bit on Init(). bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1465572 gecko-commit: d81a759c7d9557eff526c52f9c522be531aa0101 gecko-integration-branch: central gecko-reviewers: bz 07 June 2018, 12:18:26 UTC
831c3ee Emilio Cobos Álvarez 06 June 2018, 09:48:58 UTC Changing the slot name should properly invalidate layout. Just something I found while trying to construct a test-case for this. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1465572 gecko-commit: 297e6634c0a63ec5655d3b6932083d03690d5bd9 gecko-integration-branch: central gecko-reviewers: smaug 07 June 2018, 12:18:26 UTC
13365c7 David H 07 June 2018, 10:56:30 UTC Fix the TemporaryFile mode to prevent crashing. (#11382) Setting the TemporaryFile mode to 'rw+b' in request.py causes an IOError when trying to write to the _buf. Removing the mode, and using the default 'w+b', fixes this issue. Added 2 tests that test for this 07 June 2018, 10:56:30 UTC
6380b5c Anne van Kesteren 07 June 2018, 08:13:07 UTC DOM: more window.event tests To compliment #4790. 07 June 2018, 08:13:07 UTC
659fe6e Mike Taylor 07 June 2018, 06:59:30 UTC Add tests for window.event For https://github.com/whatwg/dom/issues/334 and https://github.com/whatwg/dom/pull/407. 07 June 2018, 06:59:30 UTC
ed2f4a4 Hiroki Nakagawa 07 June 2018, 06:20:37 UTC Worker: Use Document's SettingsObject for top-level module script loading on dedicated workers This CL makes Document serve its settings object ("outside settings") to WorkerGlobalScope based on the following HTML spec: Step 13. "Fetch a module worker script graph given url, outside settings, destination, the value of the credentials member of options, and inside settings." https://html.spec.whatwg.org/multipage/workers.html#worker-processing-model This SettingsObject is used as "fetch client settings object" for top-level module script loading and static imports. Before this CL, WorkerGlobalScope's settings object ("inside_settings_object") is used as "fetch client settings object". This is obviously wrong and fails some web-platform-tests. This change fixes them. Change-Id: I87a78f38308e262425b848d99dc617dbddeb81e7 Bug: 842553, 845285 Reviewed-on: https://chromium-review.googlesource.com/1084133 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#565199} 07 June 2018, 06:36:39 UTC
b8fa20c Kent Tamura 07 June 2018, 04:50:36 UTC dom: Mark dom/nodes/ParentNode-querySelector-All*.* slow. These tests sometimes time out. Bug: 850132 Change-Id: I90759388aadf121b6b744877d34bac3a61abfe53 Reviewed-on: https://chromium-review.googlesource.com/1089606 Reviewed-by: Takayoshi Kochi <kochi@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#565180} 07 June 2018, 05:08:45 UTC
5133c54 Wanming Lin 07 June 2018, 04:10:29 UTC Create permissions test suite with IDL tests (#9301) 07 June 2018, 04:10:29 UTC
087ee43 Aleks Totic 06 June 2018, 23:31:40 UTC Use correctly sized images in flexbox tests Bug: 467127 Change-Id: I4176cb0e4216ced9434c5c84832df6d6a5cd37d3 Reviewed-on: https://chromium-review.googlesource.com/1089205 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#565090} 06 June 2018, 23:42:06 UTC
6e066fd Luke Bjerring 06 June 2018, 21:44:04 UTC Revert #9854 (#11393) 06 June 2018, 21:44:04 UTC
8121170 Fadi Meawad 06 June 2018, 21:05:40 UTC [PageLifecycle] Fix WPT test by hiding the page before freezing Freezing can only work on hidden pages, currently there is no easy way in webdriver that allows us to hide the page. A new webdriver API is in the works to enable that, but meanwhile, for all testing API, we have to couple hiding with freezing. This CL does that and reenables the test with Network Service. Bug: 837709, 848604 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo Change-Id: Ib5c513aefb219cef38a563be81fe8abf4b354051 Reviewed-on: https://chromium-review.googlesource.com/1089354 Commit-Queue: Fadi Meawad <fmeawad@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#565031} 06 June 2018, 21:16:00 UTC
5684f56 Alice Boxhall 06 June 2018, 18:48:11 UTC Make focus-visible match on keypress Change-Id: I7f467623d5476f717d73aeeaecdc69399c6b65f5 Reviewed-on: https://chromium-review.googlesource.com/1074584 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#564977} 06 June 2018, 18:58:47 UTC
b7cc2f1 Geoffrey Sneddon 06 June 2018, 16:06:43 UTC Try the built-in XMLParser and then fallback to ours While this means in the worst-case we parse almost the entire file twice (when there's an entity at the end), the more common case is an unsupported encoding (which, of course, is at the start), and the most common case is never falling back. In the no-manifest case, this is 22% faster. 06 June 2018, 17:14:13 UTC
31a9531 Geoffrey Sneddon 06 June 2018, 15:52:49 UTC Pass useChardet=False for HTML files in SourceFile When chardet is installed, this makes the no-manifest case 7% faster. 06 June 2018, 17:14:13 UTC
7cd0b88 Geoffrey Sneddon 06 June 2018, 14:00:13 UTC Fix #10922: move six into third_party and update to 1.11 06 June 2018, 15:36:24 UTC
efdb898 Geoffrey Sneddon 06 June 2018, 12:52:33 UTC Fix #7200: Update vendored html5lib to 1.0.1 This adds webencodings as another vendored package, and moves both to third_party (part of #10922). 06 June 2018, 15:36:24 UTC
c7c54d3 Florian Rivoal 06 June 2018, 14:28:11 UTC Merge pull request #11365 from frivoal/git-doc-serve Mention the need to setup the web server in the github tutorial 06 June 2018, 14:28:11 UTC
e895776 Florian Rivoal 06 June 2018, 14:12:15 UTC Merge pull request #11366 from frivoal/css-text-2682 [css-text-3] Add test for intrinsic sizing and overflow-wrap 06 June 2018, 14:12:15 UTC
f110c50 Luke Bjerring 06 June 2018, 13:15:09 UTC Update the webusb IDL file (#9854) 06 June 2018, 13:15:09 UTC
892738f Manuel Rego Casasnovas 06 June 2018, 09:01:08 UTC [css-contain] Layout containment overflowing contents as ink overflow Text form the spec (https://drafts.csswg.org/css-contain/#containment-layout): "If the contents of the element overflow the element, they must be treated as ink overflow." The patch modifies LayoutBox::LayoutOverflowRectForPropagation() so the overflowing contents of an element with "contain: layout" are treated as ink overflow. That way they don't interfere at all in the layout of its ancestors. BUG=843320 TEST=external/wpt/css/css-contain/contain-layout-015.html Change-Id: Iedd47edf46a0e4ce0e4102abe5881d25771fe0fa Reviewed-on: https://chromium-review.googlesource.com/1087462 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#564826} 06 June 2018, 12:49:51 UTC
4b4c626 Hiroki Nakagawa 06 June 2018, 07:14:12 UTC Worker: Add referrer tests for ES Modules on dedicated workers Referrer handling spans multiple algorithms in multiple specs, so I leave only the entry points of them. For top-level module script loading and static imports, referrer is determined based on the "outside settings": "Fetch a module worker script graph given url, outside settings, destination, the value of the credentials member of options, and inside settings." https://html.spec.whatwg.org/multipage/workers.html#worker-processing-model For dynamic imports, referrer is determined based on the "referencing script's settings object". In this case, it's "inside settings": Step 2.4: "Fetch a module script graph given url, referencing script's settings object, "script", and options. Wait until the algorithm asynchronously completes with result." https://html.spec.whatwg.org/multipage/webappapis.html#hostimportmoduledynamically(referencingscriptormodule,-specifier,-promisecapability) These tests are still failing. Subsequent CLs will fix them. Bug: 842553 Change-Id: I3855b91c7e6ba93f5c99fb63b24b6274e6b43211 Reviewed-on: https://chromium-review.googlesource.com/1088339 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#564811} 06 June 2018, 12:42:00 UTC
7018426 Josh Matthews 06 June 2018, 12:03:38 UTC Ensure that Config's set of ports is generated atomically. (#11299) 06 June 2018, 12:03:38 UTC
f1ec951 Frédéric Wang 05 June 2018, 10:13:34 UTC Add "Do not edit" warning to all HTML pages. This aligns with the woff2-tests generator: https://github.com/w3c/woff2-tests/pull/12 https://github.com/w3c/woff2-tests/pull/14 06 June 2018, 12:03:05 UTC
d3f1672 Matt Falkenhagen 06 June 2018, 02:40:15 UTC Make fetch-event.https.html faster. It was registering a service worker for each test case, and had a lot of test cases. This changes the file to register a single service worker at the beginning, and unregister it at the end. Bug: 847787 Change-Id: Ic2536824a3c57e86bb5e042287e9e62e6222ad9a Reviewed-on: https://chromium-review.googlesource.com/1087188 Reviewed-by: Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#564770} 06 June 2018, 11:58:05 UTC
7250b3a Florian Rivoal 06 June 2018, 09:13:48 UTC [css-text-3] Add exlanation comment in test 06 June 2018, 09:13:48 UTC
1421a4a Jake Archibald 06 June 2018, 07:25:17 UTC Fetch: test identity encoding for range requests For https://github.com/whatwg/fetch/pull/751. 06 June 2018, 07:25:17 UTC
8a0639c Florian Rivoal 06 June 2018, 06:59:25 UTC fix typo 06 June 2018, 06:59:25 UTC
67adfa1 Anny Gakhokidze 04 June 2018, 19:20:48 UTC Part 2: Prevent content sniffing of the response in original echo-content.py The changes made to echo-content.py are the same as the ones made in Bug 1435781. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1351193 gecko-commit: 74219e6cc8b0baab1c2eb7c7127007e3b7bfcd33 gecko-integration-branch: mozilla-inbound gecko-reviewers: nika 06 June 2018, 06:20:29 UTC
3bcea64 Emilio Cobos Álvarez 05 June 2018, 00:58:06 UTC Make pseudo-elements work with :host. Imported WebKit's test as a WPT. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1465291 gecko-commit: bb430edf217ece760c5fda5796d776f2256f90e3 gecko-integration-branch: mozilla-inbound gecko-reviewers: xidorn 06 June 2018, 05:57:43 UTC
f909ee1 Florian Rivoal 06 June 2018, 00:47:26 UTC [css-text-3] Add test for intrinsic sizing and overflow-wrap This test goes toghether with the spec changes for https://github.com/w3c/csswg-drafts/issues/2682 06 June 2018, 00:47:26 UTC
c0fbd59 Manuel Rego Casasnovas 05 June 2018, 20:19:46 UTC [css-contain] Disable layout containment for certain elements Text from the spec (https://drafts.csswg.org/css-contain/#containment-layout): "... if the element is an internal table element other than display: table-cell, or if the element is an internal ruby element, or if the element’s principal box is a non-atomic inline-level box, layout containment has no effect." The patch disables "contain: layout" for internal table elements but table cells, internal ruby elements and non-atomic inline-level boxes. Some of the new tests pass or fail incidentally due to crbug.com/785212, once that's fixed all the tests should be working as expected. BUG=843329 TEST=external/wpt/css/css-contain/contain-layout-008.html TEST=external/wpt/css/css-contain/contain-layout-009.html TEST=external/wpt/css/css-contain/contain-layout-010.html TEST=external/wpt/css/css-contain/contain-layout-011.html TEST=external/wpt/css/css-contain/contain-layout-012.html TEST=external/wpt/css/css-contain/contain-layout-013.html TEST=external/wpt/css/css-contain/contain-layout-014.html Change-Id: I5f0893a9ce69dc8e76cf16acb1b8556bf0e02adf Reviewed-on: https://chromium-review.googlesource.com/1087268 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#564631} 05 June 2018, 23:41:04 UTC
57285cd Raymond Toy 05 June 2018, 20:19:39 UTC Reland "WaveShaper must output non-zero values even if input is silent" This is a reland of 325b492fe733ba4c8b2128069a0a232fea1789e3 Initialize tail_time_ in constructor so we don't have uninitialized variable. Original change's description: > WaveShaper must output non-zero values even if input is silent > > If the curve for the WaveShaperNode is such that a zero input produces > a non-zero output, the WaveShaperNode needs to output that value even > if the input is silent (or disconnected). > > Do this by setting the tail time of the processor to 0 or infinity > depending on whether the curve specifies an output value of zero or > not, respectively. > > Bug: 807301 > Test: WaveShaper/silent-inputs.html > Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b > Reviewed-on: https://chromium-review.googlesource.com/896266 > Commit-Queue: Raymond Toy <rtoy@chromium.org> > Reviewed-by: Hongchan Choi <hongchan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#564186} Bug: 807301 Change-Id: I866c5b303b40c1245d86daf43c592eed39d6a9c9 Reviewed-on: https://chromium-review.googlesource.com/1087427 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#564630} 05 June 2018, 23:13:50 UTC
8bafc09 Aleks Totic 05 June 2018, 20:19:32 UTC [LayoutNG] Fix flex BODY in quirks mode We were not updating margins correctly inside NGBlockNode::RunOldLayout. Symptom was that BODY(flex) block size was too big when HTML had margins inside quirks mode. Another side effect of this fix is two crashes have gone away. Added explicit test case for BODY(flex) in quirks mode. Bug: 849490 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Id0ce0910144c81fc254646110424f36c898f9ebd Reviewed-on: https://chromium-review.googlesource.com/1086381 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#564629} 05 June 2018, 22:43:20 UTC
5e0fea3 Simon Pieters 05 June 2018, 22:31:01 UTC Fix bugs in split-up encoding tests Bugs were introduced in d6c29bef8d4bcdfe4f689defca73360b07647d71 * Some script paths were wrong * A big5 test referenced eucjpEncoder instead of big5Encoder * That big5 test also referenced encode-form-common.js instead of encode-href-common.js Fixes #11015. Also add code to generate variants. 05 June 2018, 22:31:01 UTC
a7683a8 Chris Lilley 05 June 2018, 22:08:28 UTC Merge pull request #11326 from web-platform-tests/woff2-sync-up-available WOFF2: Sync up available-* tests against https://github.com/w3c/woff2-tests 05 June 2018, 22:08:28 UTC
40ff5f9 Chris Lilley 05 June 2018, 22:08:07 UTC Merge pull request #11313 from web-platform-tests/woff2-sync-up Sync up tests against https://github.com/w3c/woff2-tests 05 June 2018, 22:08:07 UTC
096cc8f Manuel Rego Casasnovas 05 June 2018, 20:19:43 UTC Merge pull request #11324 from Loirooriol/css-logical-longhands Add test for logical box model longhand properties 05 June 2018, 20:19:43 UTC
a21cb02 Dominic Farolino 05 June 2018, 19:25:49 UTC Add tests that deal with applying number format specifiers on Symbols 05 June 2018, 19:25:49 UTC
e8fb48b Luke Bjerring 05 June 2018, 15:00:50 UTC Auto-update the payment-request IDL 05 June 2018, 15:00:50 UTC
d564a34 Geoffrey Sneddon 16 May 2018, 16:24:02 UTC Make --verify-log-full not override log level 05 June 2018, 14:40:07 UTC
5bd42c1 Geoffrey Sneddon 14 May 2018, 14:46:42 UTC Fix #10921: make --stability use the same code as --verify 05 June 2018, 14:40:07 UTC
38809cb Geoffrey Sneddon 14 May 2018, 15:17:42 UTC Make check_stability.py use the --verify code Note this doesn't yet address #9874, as it currently only runs the repeat_restart mode of --verify (as it did previously). 05 June 2018, 14:40:07 UTC
60a937d Simon Pieters 05 June 2018, 10:06:22 UTC Make IndexedDB/support.js work in workers This should fix the test html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/serialization-via-idb.any.worker.html Part of #11269. 05 June 2018, 13:49:07 UTC
30eb26b Oriol Brufau 04 June 2018, 11:18:12 UTC Add tests for logical box model longhand properties Based on Mozilla's layout/style/test/test_logical_properties.html 05 June 2018, 13:46:08 UTC
ec9ffb1 David H 05 June 2018, 13:42:21 UTC Redirect POST requests using .py resource Part of #11269. Also see #11343. 05 June 2018, 13:42:21 UTC
8b089cb Geoffrey Sneddon 05 June 2018, 12:17:22 UTC Test for used column-count when column-count/width are not auto (#10250) 05 June 2018, 12:17:22 UTC
7a80bc9 Manuel Rego Casasnovas 05 June 2018, 11:59:18 UTC Merge pull request #11352 from mrego/contain-layout-fixes [css-contain] Fix references to paint instead of layout containment 05 June 2018, 11:59:18 UTC
8c28134 Manuel Rego Casasnovas 05 June 2018, 11:40:25 UTC [css-contain] Fix references to paint instead of layout containment 05 June 2018, 11:40:25 UTC
1706eb3 Anne van Kesteren 13 March 2017, 13:13:51 UTC XMLHttpRequest: upload listener flag Tests for https://github.com/whatwg/xhr/issues/95. 05 June 2018, 11:29:32 UTC
aa5ec97 Morten Stenshorne 05 June 2018, 11:07:10 UTC [LayoutNG] Need to know when establishing a new FC during min/max calculation. When we have to lay out an object to determine its min/max inline size, and the node establishes a new formatting context, we need to create a constraint space that reflects this. The block size of the float needs to be included in the block size of its container, because this block size will be the min/max preferred inline size of the container of that container, if the writing modes are orthogonal. Avoid some duplicate code for creating the constraint space builder. The second builder, the one that redoes layout with infinite available space now gets SetFloatsBfcOffset() called, which was previously missing, but that must have been an oversight. This fixes the recently introduced regression with fast/multicol/vertical-rl/column-rules.html and also another test. Wrote a new test that tests exactly what I wanted to fix as well. Bug: 847807 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I7b28a0ef8061fc3089deb488ad0a78b81776295d Reviewed-on: https://chromium-review.googlesource.com/1084989 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#564438} 05 June 2018, 11:15:36 UTC
e4fd758 Simon Pieters 05 June 2018, 08:31:01 UTC HTML: Fix sandbox-disallow-same-origin.html to expect SecurityError Part of #11269. 05 June 2018, 09:56:26 UTC
2b0cd61 Anne van Kesteren 05 June 2018, 09:34:38 UTC Fetch: port blocking change (427, 548, 6697) See https://github.com/whatwg/fetch/pull/738. 05 June 2018, 09:34:38 UTC
dae7535 Dominic Farolino 05 June 2018, 08:50:29 UTC Experimental Priority Hints support on fetch() API Adding support for Priority Hints on the fetch() API under an experimental flag. This adds the notion of importance to core/fetch code, and adds a new member to the RequestInit dictionary to communicate developer-specified "importance" downstream. R=kinuko@chromium.org, kouhei@chromium.org, yhirano@chromium.org, yoav@yoav.ws Bug: 821464 Change-Id: Ib96a128d77004029e86122c07552250c697dea5f Reviewed-on: https://chromium-review.googlesource.com/1084063 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Commit-Queue: Dominic Farolino <domfarolino@gmail.com> Cr-Commit-Position: refs/heads/master@{#564410} 05 June 2018, 08:58:52 UTC
b20cb44 Simon Pieters 05 June 2018, 07:26:54 UTC HTML: Change <td hidden> and <th hidden> to expect display: none Follows https://github.com/whatwg/html/pull/3736. 05 June 2018, 07:51:59 UTC
2bd11b9 jugglinmike 05 June 2018, 04:22:55 UTC [wptrunner] End Sauce Connect process gracefully (#11334) Previously, the Sauce Connect process was closed gracefully in response to prolonged period of inactivity. This procedure was not used under normal operating conditions. Factor graceful shutdown logic into a new method, `quit`, and reuse this method to end the process following successful test completion. 05 June 2018, 04:22:55 UTC
fa5ee47 Matt Giuca 05 June 2018, 03:57:19 UTC Revert "WaveShaper must output non-zero values even if input is silent" This reverts commit 325b492fe733ba4c8b2128069a0a232fea1789e3. Reason for revert: Broke webaudio/.../waveshaper-364379.html in webkit_layout_tests. See https://crbug.com/849535 Original change's description: > WaveShaper must output non-zero values even if input is silent > > If the curve for the WaveShaperNode is such that a zero input produces > a non-zero output, the WaveShaperNode needs to output that value even > if the input is silent (or disconnected). > > Do this by setting the tail time of the processor to 0 or infinity > depending on whether the curve specifies an output value of zero or > not, respectively. > > Bug: 807301 > Test: WaveShaper/silent-inputs.html > Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b > Reviewed-on: https://chromium-review.googlesource.com/896266 > Commit-Queue: Raymond Toy <rtoy@chromium.org> > Reviewed-by: Hongchan Choi <hongchan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#564186} TBR=rtoy@chromium.org,hongchan@chromium.org Change-Id: I29fd96b1a9dd2b87db12867031399b069beba706 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 807301, 849535 Reviewed-on: https://chromium-review.googlesource.com/1086647 Reviewed-by: Matt Giuca <mgiuca@chromium.org> Commit-Queue: Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#564359} 05 June 2018, 04:05:45 UTC
8a5301b Justin Ribeiro 05 June 2018, 02:49:41 UTC custom-elements: Element created by createElement(name, options) with valid custom element name and options set to undefined should be upgraded createElement('my-element', undefined) was not being upgraded, though both createElement('my-element') and createElement('my-element', {}) were. Bug: 841725 Change-Id: Id43b21f8e1cad10745dedf3699691da7ad85cf03 Reviewed-on: https://chromium-review.googlesource.com/1084007 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#564352} 05 June 2018, 02:57:15 UTC
ce1bb88 Florian Rivoal 05 June 2018, 00:17:00 UTC Mention the need to setup the web server in the github tutorial 05 June 2018, 00:17:00 UTC
dc60bfc Yi Gu 04 June 2018, 22:50:55 UTC Compute correct sticky box constraints within scrollable containers Currently calculating the skipped offset between sticky and its containing block assumes that the latter is not scrollable. However, when it is we should ignore the scroll offset from the container otherwise scrolling the container would cause the sticky offset incorrectly double accumulated. Bug: 841551 Change-Id: Ib49aaa74808847dcf6fce7dc0db9ac4d2de06c64 Reviewed-on: https://chromium-review.googlesource.com/1054488 Commit-Queue: Yi Gu <yigu@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#564276} 04 June 2018, 23:00:24 UTC
4f7d096 Simon Pieters 04 June 2018, 20:06:55 UTC Make multiple-workers tests fail if (Shared)Worker is not defined Fixes #11222. Part of #11269. 04 June 2018, 20:06:55 UTC
5007510 Raymond Toy 04 June 2018, 19:43:41 UTC WaveShaper must output non-zero values even if input is silent If the curve for the WaveShaperNode is such that a zero input produces a non-zero output, the WaveShaperNode needs to output that value even if the input is silent (or disconnected). Do this by setting the tail time of the processor to 0 or infinity depending on whether the curve specifies an output value of zero or not, respectively. Bug: 807301 Test: WaveShaper/silent-inputs.html Change-Id: I6539d2e00f5d3e624ffaf2810944eb6d53d6f84b Reviewed-on: https://chromium-review.googlesource.com/896266 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#564186} 04 June 2018, 20:01:43 UTC
4b77fc9 Brian Birtles 04 June 2018, 03:09:48 UTC Update event-dispatch test now that we can use the updated EventWatcher bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: d87bf0bd52e2398d47501e88abdf7b290b4f424c gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
2031f81 Brian Birtles 04 June 2018, 03:09:44 UTC Add spec links to test files bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: 1156ef220859015269bff058a3db9f6183bf347f gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
7874493 Brian Birtles 04 June 2018, 03:09:40 UTC Move CSS animations / Web animation integration tests to web-platform-tests bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: 4a4aafa588f86050dadc4ea7644639e4ac547461 gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
2160e0f Brian Birtles 04 June 2018, 03:09:37 UTC Update test_animation-starttime.html This patch updates the tests in this file as follows: * startTime of a newly created (play-pending) animation is unresolved -> Covered by 'startTime of a play-pending animation is unresolved' in wpt/web-animations/interfaces/Animation/startTime.html However, it would be useful to have a test a new CSS animation is play-pending so I have extended the test in test_animation-playstate.html to cover this. * startTime of a newly created (pause-pending) animation is unresolved -> Covered by 'startTime of a pause-pending animation is unresolved' in wpt/web-animations/interfaces/Animation/startTime.html * startTime is resolved when running -> Covered by 'startTime is resolved when running' in wpt/web-animations/interfaces/Animation/startTime.html * startTime is unresolved when paused -> Moved to wpt/web-animations/timing-model/animations/pausing-an-animation.html * startTime while pause-pending and play-pending -> Moved to wpt/web-animations/timing-model/animations/pausing-an-animation.html * startTime while play-pending from finished state, startTime while play-pending from finished state using finish() -> Merged and moved to wpt/web-animations/timing-model/animations/playing-an-animation.html * Pausing should make the startTime become null -> Simplified and merged into the test for 'startTime is unresolved when paused' / 'Pausing clears the start time' test in wpt/web-animations/timing-model/animations/pausing-an-animation.html * Sanity test to check round-tripping assigning to a new animation's startTime -> Updated and left. * Skipping forward through animation -> This is really testing two things: (a) That you can seek a CSS animation using the start time. For this it makes sense to have a separate test that also checks that the computed style is updated (like we have for current time). (b) That seeking a CSS animation using the start time triggers dispatching events. This patch splits the above into two separate tests. * Skipping backwards through animation, Redundant change, before -> active, then back, Redundant change, before -> after, then back, Redundant change, active -> before, then back, Redundant change, active -> after, then back, Redundant change, after -> before, then back, Redundant change, after -> active, then back -> All these tests are really just exercising event dispatch which is already covered by test_event-dispatch.html. Provided we have a test that checks that events are dispatched when setting the startTime we don't need to test each combination again since we have tests for each of these combinations already when using the currentTime to seek and we can assume UAs are following the same code path at this point. As a result this patch drops these tests. * Setting startTime to null -> Covered by 'Setting an unresolved start time sets the hold time' in wpt/web-animations/timing-model/animations/setting-the-start-time-of-an-animation.html * Animation.startTime after pausing -> Covered by the new 'Pausing clears the start time' test in wpt/web-animations/timing-model/animations/pausing-an-animation.html * Animation.startTime after canceling -> Merged into wpt/web-animations/timing-model/animations/canceling-an-animation.html and made it follow the spec a little more closely (which requires clearing the start time and hold time). bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: bfe96f889a3bf706cba047baadbbd67fdd6a6414 gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
df00d56 Brian Birtles 04 June 2018, 03:09:33 UTC Move the reversing test to Web Animations web-platform-tests bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: 357a5f2a456bd31c83ae54933dec03ae6af0a12d gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
5048439 Brian Birtles 04 June 2018, 03:09:29 UTC Tidy up test_animation-ready.html Although many of these tests are similar to tests in the Web Animations web-platform-tests test suite they focus on the interaction with animation-play-state and so are probably worth keeping. There are two exceptions that I felt were worth changing: * The test for the handling of a ready promise on an aborted pause. I could not find a similar test in the Web Animations wpt and the test is not really particular to CSS animations so this patch moves it to Web Animations wpt. * The test for the resolution value of the ready promise for a paused animation is covered by the "A pending ready promise should be resolved and not replaced when the animation is paused" in pausing-an-animation.html in the Web Animations wpt (although peripherally) and that seems like the better place for this test anyway (it is not specific to CSS animations) so I have simply deleted it from this file. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: 225a32bacfbc737e9934ba301fc447ce58e500c8 gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
0a51201 Brian Birtles 04 June 2018, 03:09:25 UTC Re-arrange tests in test_animations-currenttime.html A number of these tests are redundant with other tests or are otherwise unnecessary. Other tests should be moved to a more appropriate file. Some notable examples: * A number of the tests relate to dispatching events in various phases and have been moved to test_event-dispatch.html. * The "Seeking finished -> paused dispatches animationstart" test is covered by the "After -> Active" test in test_event-dispatch.html (which also operates on a paused animation). * The "Animation.currentTime clamping" is really just testing finishing behavior and is covered by the updating-the-finished-state.html tests in the Web Animations web-platform-tests (specifically the "Updating the finished state when playing past end" test). * Likewise for the "Animation.currentTime clamping for reversed animation" test. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466031 gecko-commit: bdf0455bd3ecfc5c79b305cd36db71bff86f099d gecko-integration-branch: mozilla-inbound gecko-reviewers: hiro 04 June 2018, 19:21:36 UTC
6e44ea9 Christoph Kerschbaumer 04 June 2018, 13:14:04 UTC Fix race condition within wpt test policy-inherited-correctly-by-plznavigate.html. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1466508 gecko-commit: 0c71a38c8c5c49d3041a3a8d06116b07ba1279b3 gecko-integration-branch: mozilla-inbound gecko-reviewers: jgraham 04 June 2018, 18:20:11 UTC
1e64b41 youennf 04 June 2018, 16:53:29 UTC Merge pull request #11319 from youennf/wpt-export-for-webkit-186254 WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186254 04 June 2018, 16:53:29 UTC
e276a8b joanmarie 04 June 2018, 16:00:09 UTC Core-AAM: Add tests for blockquote, caption, and paragraph roles (#11327) 04 June 2018, 16:00:09 UTC
64f8dcf Blink WPT Bot 04 June 2018, 15:16:36 UTC Clarify expectations for failing cookie tests (#8584) These clean ups are split out from https://crrev.com/c/788217: - Defining the assert failure messages Change-Id: I74ba2bb70e907a28292301046a7433480ab669d8 04 June 2018, 15:16:36 UTC
b4073eb Frédéric Wang 04 June 2018, 13:20:47 UTC WOFF2: Sync up available-* tests against https://github.com/w3c/woff2-tests 04 June 2018, 13:21:02 UTC
3b8c1c4 Florian Rivoal 04 June 2018, 12:45:18 UTC Update git documentation (#11322) Remove parts that are no longer relevant (we only have one repo now, we no longer use submodules...), and update graphics. Related to #5301 04 June 2018, 12:45:18 UTC
8e487e0 Frédéric Wang 04 June 2018, 12:27:07 UTC Regenerated test index for WOFF2. 04 June 2018, 12:27:18 UTC
6ce1b0b Frédéric Wang 04 June 2018, 12:22:40 UTC Remove obsolete WOFF2 tests for metadata display. 04 June 2018, 12:26:12 UTC
387c22c Frédéric Wang 04 June 2018, 12:21:31 UTC Add new WOFF2 tests: directory-knowntags-001 and tabledata-glyf-origlength-003. 04 June 2018, 12:21:31 UTC
018f058 Frédéric Wang 02 June 2018, 06:22:17 UTC Update assert, help, titles to match current ouput of w3c/woff2-tests 04 June 2018, 12:11:10 UTC
cfae5d2 Frédéric Wang 01 June 2018, 22:46:49 UTC Remove extra space from '<link rel="reviewer" title="Chris Lilley"' The following command was applied: sed -i 's/<link rel/<link rel/' *.xht This matches the current spacing from https://github.com/w3c/woff2-tests 04 June 2018, 12:11:10 UTC
c667649 Ms2ger 01 June 2018, 12:22:12 UTC Remove unused environment import. 04 June 2018, 12:06:13 UTC
2d02508 Guido Urdaneta 04 June 2018, 10:15:06 UTC Do not allow the empty string as a facingMode constraint value for MediaStreams. The empty string is an invalid facingMode value that was being interpreted to be equivalent to the internal facing-mode value of NONE. Bug: 814309 Change-Id: I260fbc41fd17a8bdcd1ca63baffe3bed14f3c4ab Reviewed-on: https://chromium-review.googlesource.com/1072471 Reviewed-by: Harald Alvestrand <hta@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#564046} 04 June 2018, 10:24:41 UTC
0b66b59 Simon Pieters 04 June 2018, 09:14:06 UTC [css-paint-api] Fail a reftest early if CSS.registerProperty is not supported Part of #11269. Also fix remaining instances of CSS.registerProperty 04 June 2018, 09:14:06 UTC
6ed8b90 Kenichi Ishibashi 04 June 2018, 08:50:56 UTC Add a WPT for Service-Worker header The spec requires that an HTTP request to fetch a service worker script has 'Service-Worker: script' header[1]. [1] https://w3c.github.io/ServiceWorker/#update-algorithm Bug: 848265 Change-Id: I76c836fcf43d287bcac910c3655e5b127ad8555c Reviewed-on: https://chromium-review.googlesource.com/1082253 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#564023} 04 June 2018, 09:00:24 UTC
5b2eb3f Michael[tm] Smith 04 June 2018, 07:45:52 UTC cc Update messages.json 04 June 2018, 07:47:46 UTC
f1815a9 Ms2ger 01 June 2018, 15:37:31 UTC Add filtering support to ManifestLoader. In some use cases, the overhead of creating data structures for all tests in the manifest, and then filtering them, is too big. This change allows users to filter tests when initially creating the manifest. 04 June 2018, 07:02:35 UTC
22d7d74 Youenn Fablet 04 June 2018, 05:03:07 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186254 04 June 2018, 05:03:07 UTC
ee82278 Jungkee Song 03 June 2018, 22:18:48 UTC Merge pull request #11315 from web-platform-tests/importscripts-fix Correct importScripts() behavior test 03 June 2018, 22:18:48 UTC
15951e2 Jungkee Song 02 June 2018, 21:55:41 UTC Correct importScripts() behavior test - Update the after-install call to expect NetworkError instead of TypeError. - Initialize echo_output before calling importScripts(). 02 June 2018, 21:55:41 UTC
back to top