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
da25c99 Anne van Kesteren 06 June 2018, 09:55:14 UTC move service worker into resources too 06 June 2018, 09:55:14 UTC
4fcb0f3 Anne van Kesteren 15 April 2018, 13:08:53 UTC rename resources 06 June 2018, 09:48:32 UTC
3776e19 Anne van Kesteren 15 April 2018, 12:54:17 UTC address wait_for_state, cleanup, and style issues 06 June 2018, 09:48:32 UTC
b5b8dd2 Anne van Kesteren 12 April 2018, 17:29:14 UTC Test for opaque redirect handling As per https://github.com/whatwg/fetch/pull/633#issuecomment-346610876 except using global state instead of the cache API. (Improvements welcome!) 06 June 2018, 09:48:32 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
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
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
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
1dc612f Jinho Bang 02 June 2018, 01:49:54 UTC PaymentHandler: Fix a crash when creating event object with empty data The following codes cause crashes in current implementation. - new CanMakePaymentEvent("canmakepaymentevent", {}); - new PaymentRequestEvent("paymentrequestevent", {}); This patch fixes the problem and fixes/adds WPT tests. Bug: none Change-Id: I95375f1148d69a17075d393990e3726ad2bf1cf3 Reviewed-on: https://chromium-review.googlesource.com/1070957 Commit-Queue: Jinho Bang <jinho.bang@samsung.com> Reviewed-by: Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#563903} 02 June 2018, 01:59:15 UTC
69a48d9 Ehsan Karamad 02 June 2018, 01:40:00 UTC Revert "Cleanup plugin element frames when the layout tree is detached" This reverts commit 596e6b3281a8cc2c4b646553e4cde169a29a1d1d. Reason for revert: DetachLayoutTree could be called at inopportune times such as style recalc or during layout. This caused several crashes. Original change's description: > Cleanup plugin element frames when the layout tree is detached > > Unlike frames, plugin elements (<embed> and <object>) are updated > when their layout tree is rebuilt. However, due to an oversight, > <embed> or <object> elements displaying subframes would only have > the associated content view (FrameView) torn down, leaving a > dangling content frame. > > This led to some interesting side effects: > - When transitioning from a local frame to a plugin, the content > frame would remain live, with JS still happily running. > - When transitioning from a remote frame to a plugin, > - When navigating a remote frame from one URL to another, the > element would stop updating since the FrameView would be torn > down but a new one would never be created. Note that this was > not (as much of) a problem for local frames, since local frames > re-create the LocalFrameView on every navigation. > With this CL, if a plugin element has an associated content frame, > use that to clean up the state associated with the element when the > layout tree is detached. This can cause the browser context to be > re-created: this matches the behavior of Edge and Firefox. > > Note that there is still one edge case where Blink behaves oddly: > if the navigation fails and should display fallback content, the > content frame still remains attached. This will be addressed in > followups. > > Link to whatwg issue: https://github.com/whatwg/html/issues/3576 > > Bug: 776510, 781880 > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng > Change-Id: Id18605fbe602ea6c0076c1d579345cdcf28cc984 > Reviewed-on: https://chromium-review.googlesource.com/996314 > Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Alex Moshchuk <alexmos@chromium.org> > Cr-Commit-Position: refs/heads/master@{#561768} TBR=dcheng@chromium.org,creis@chromium.org,alexmos@chromium.org,ekaramad@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 776510, 781880, 847216, 846708 Change-Id: I762631b92463352bea9bf3102d90a13b72776786 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Reviewed-on: https://chromium-review.googlesource.com/1083500 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Ehsan Karamad <ekaramad@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#563902} 02 June 2018, 01:49:49 UTC
dcc00e1 Simon Pieters 01 June 2018, 20:17:17 UTC HTML: Don't confuse test runner by including testharness.js in a popup Part of #11269. 01 June 2018, 20:17:17 UTC
04cea7f Simon Pieters 01 June 2018, 20:15:56 UTC Make dynamic-import tests fail early instead of time out Part of #11269. 01 June 2018, 20:15:56 UTC
bbb74f3 François REMY 01 June 2018, 18:54:55 UTC Update outline-017.html & 018 to reduce flakiness in Edge 01 June 2018, 18:54:55 UTC
748214c L. David Baron 01 June 2018, 18:50:05 UTC Sync Mozilla tests as of https://hg.mozilla.org/mozilla-central/rev/9900cebb1f9000bd05731ba67736b7c51f7eb812 . (#11283) 01 June 2018, 18:50:05 UTC
135d656 Mike Pennisi 01 June 2018, 15:37:04 UTC fixup! [mediacapture] Simply test and use standard API 01 June 2018, 18:19:42 UTC
d2a2ea6 Mike Pennisi 29 May 2018, 00:38:37 UTC [mediacapture] Simply test and use standard API The MediaStream's `active` event was removed from the specification in December of 2015 [1]. The `addtrack` event offers similar semantics, and as a standard API, it is expected to be implemented by all browsers which follow the specification. In addition, because it does not depend on media playback, its use allows `MediaElement#play` to be removed. That removal simplifies the process of executing the test because browsers are beginning to tighten their policies regarding automated media playback [2]. [1] https://github.com/w3c/mediacapture-main/pull/291 [2] https://developers.google.com/web/updates/2017/09/autoplay-policy-changes 01 June 2018, 18:19:42 UTC
ff4d055 Ian Kilpatrick 01 June 2018, 16:38:27 UTC [css-layout-api] Adds passing of LayoutConstraints#fixedBlockSize. This passes a fixed block size constraint into the layout function if: - It has a fixed/percentage/calc block-size. - The abs-pos constraints will make a fixed block size. - It is a quirky body/document (which stretches to fit the viewport). - It has a fixed block-size constraint from a parent layout. The tests all behave the same way. The layout which we are interested in testing looks at the received fixedBlockSize, and if correct performs layout on the only child with a 100x100 fixed size. Bug: 726125 Change-Id: I4eec86a843d58a791c9df071e16b71bf2f5d80ee Reviewed-on: https://chromium-review.googlesource.com/1073636 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#563668} 01 June 2018, 16:57:32 UTC
197cdad Chris Nardi 01 June 2018, 15:26:36 UTC Move add_dependency_idls after add_idls (#11305) Per #11280, the order in which you call these methods matters to execution. Flip the order in order to prevent `Unrecognized type EventHandler`. 01 June 2018, 15:26:36 UTC
596c572 Simon Pieters 01 June 2018, 13:03:03 UTC HTML: split out navigation tests for URL query-encoding tests Part of #11269 and #4934. 01 June 2018, 14:46:14 UTC
b14e923 Philipp Hancke 31 May 2018, 12:04:52 UTC webrtc wpt: check signalingState before addIceCandidate in order to avoid issues with calling addIceCandidate when the peerconnection is closed BUG=836871 Change-Id: I698f5365a4e1b72a812fbc5e3adf5e51586718a6 Reviewed-on: https://chromium-review.googlesource.com/1079550 Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#563196} 01 June 2018, 14:03:10 UTC
75c1b74 Jan-Ivar Bruaroey 17 May 2018, 19:47:17 UTC Add t.step_func() to calllback and remove closed state test. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1462179 gecko-commit: f67ebc5b1596dca084bbfc13438cca0c276354cd gecko-integration-branch: autoland gecko-reviewers: bwc 01 June 2018, 12:29:50 UTC
e2fe8bb Manuel Rego Casasnovas 01 June 2018, 11:09:35 UTC [css-contain] Disable size containment for certain elements Text from the spec (https://drafts.csswg.org/css-contain/#containment-size): "... if the element is an internal table element, or if the element is an internal ruby element, or if the element’s principal box is a non-atomic inline-level box, size containment has no effect." The patch disables "contain: size" for internal table elements, internal ruby elements and non-atomic inline-level boxes. BUG=843329 TEST=external/wpt/css/css-contain/contain-size-005.html TEST=external/wpt/css/css-contain/contain-size-006.html TEST=external/wpt/css/css-contain/contain-size-007.html TEST=external/wpt/css/css-contain/contain-size-008.html TEST=external/wpt/css/css-contain/contain-size-009.html TEST=external/wpt/css/css-contain/contain-size-010.html TEST=external/wpt/css/css-contain/contain-size-011.html TEST=external/wpt/css/css-contain/contain-size-012.html Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ie3264b5c76eb04ec97064b3da8706d840924597f Reviewed-on: https://chromium-review.googlesource.com/1080799 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#563586} 01 June 2018, 11:19:10 UTC
b1a1415 Chris Nardi 01 June 2018, 03:40:02 UTC Check if a type is a sequence through idlType.generic idlType.sequence was removed in https://github.com/w3c/webidl2.js/pull/175, as the same check can be achieved through `idlType.generic === "sequence"`. Move to this more updated syntax so that updating webidl2.js will require less work the next time we do it. 01 June 2018, 10:17:27 UTC
1506a16 Yoav Weiss 01 June 2018, 07:57:57 UTC Merge pull request #11289 from web-platform-tests/domfarolino/priority-hints-owners Add Priority Hints OWNERS 01 June 2018, 07:57:57 UTC
728d78e Dominic Farolino 01 June 2018, 07:18:33 UTC Add Priority Hints OWNERS 01 June 2018, 07:18:33 UTC
bcee33a Anne van Kesteren 01 June 2018, 06:43:18 UTC URL: correct instructions for testing URL's base argument Fixes #11287. 01 June 2018, 07:14:57 UTC
5aa06e7 Dominic Farolino 01 June 2018, 06:34:33 UTC Add Priority Hints support to link and img elements This adds Priority Hints support to link and img elements under a runtime-enabled flag. The support for link elements do not extend <link rel=modulepreload>s due to the nature of module script fetching. Support for this as well as script elements in general will come at a later time due to the significant changes to the module script loading infrastructure. Intent to Implement: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/65lfM2f0eeM R=kinuko@chromium.org, kouhei@chromium.org, yhirano@chromium.org, yoav@yoav.ws Bug: 821464 Change-Id: I5ab0a114ee2b2fce9f0df6c4c5e1f7a487980d0a Reviewed-on: https://chromium-review.googlesource.com/1067245 Commit-Queue: Dominic Farolino <domfarolino@gmail.com> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Yoav Weiss <yoav@yoav.ws> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#563550} 01 June 2018, 06:43:42 UTC
ee6c9d3 Simon Pieters 31 May 2018, 14:17:19 UTC [web-animations] Fix timeout/0 tests in unsupporting browsers Part of #11269. 01 June 2018, 06:17:00 UTC
dcdd59c Simon Pieters 01 June 2018, 05:12:50 UTC Avoid uncaught exception in iframe if WebNFC is not supported (#11271) Part of #11269. 01 June 2018, 05:12:50 UTC
5679faa Hiroki Nakagawa 01 June 2018, 04:32:02 UTC Worker: Add CSP tests for ES Modules on dedicated workers Bug: 680046 Change-Id: I066d4b7750bbec00397466daac48e9d0a2ba70c0 Reviewed-on: https://chromium-review.googlesource.com/1078947 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#563531} 01 June 2018, 04:41:58 UTC
8e1adf3 Ella Ge 01 June 2018, 02:29:32 UTC remove createTouchList This Cl removes document.createTouchList and related tests. Use count is drop to a safer value, ready to remove in M69. UseCounter: https://www.chromestatus.com/metrics/feature/timeline/popularity/2368 intent to deprecate and Remove: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GLbUpUUnQzc PR to touch-events spec: https://github.com/w3c/touch-events/pull/96 Bug: 518868 Change-Id: Ia4451d0d32bf5bbb6d9c9c543ac77187c5161b42 Reviewed-on: https://chromium-review.googlesource.com/1055799 Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by: Bo <boliu@chromium.org> Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Rick Byers <rbyers@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#563490} 01 June 2018, 02:39:43 UTC
b792706 Chris Nardi 01 June 2018, 01:38:43 UTC Correct serialization of URL in background-332.html (#10478) * Correct serialization of URL in background-332.html According to https://drafts.csswg.org/cssom/#serialize-a-url, the serialization of a URL always includes double-quotes, and per https://drafts.csswg.org/css-values/#relative-urls, if a URL appears in a computed style, it is resolved to an absolute URL. Adjust background-332.html to match the spec, and update the test description to clarify the computed style is being tested. 01 June 2018, 01:38:43 UTC
72c7cfe Hiroki Nakagawa 01 June 2018, 01:16:38 UTC Worker: Change the default credentials option from 'omit' to 'same-origin' This is a follow-up for the spec change: https://github.com/whatwg/html/pull/3656 Note that ES Modules for dedicated workers is still behind the flag and this change doesn't affect applications in the real world. Bug: 848247 Change-Id: I25083f3f11f9d13663e16e2f4c137095e9b12b01 Reviewed-on: https://chromium-review.googlesource.com/1080668 Reviewed-by: Matt Falkenhagen <falken@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#563465} 01 June 2018, 01:27:25 UTC
82b2789 Javier Fernandez 29 May 2018, 13:42:15 UTC [css-grid] Baseline alignment inside the tracks sizing algorithm We have identified several cases where the Baseline Alignment accounts for the grid's intrinsic size. Since we depend on the track sizing algorithm to compute the grid's intrinsic size, the only way to handle all these cases is to integrate the baseline alignment logic in the algorithm. Additionally, the CSSWG has identified several cases that can't be solved properly; such cases have in common that they imply cyclic dependencies between the item's and grid area's size. The CSSWG has resolved that these items don't participate in baseline alignment: https://github.com/w3c/csswg-drafts/issues/1365 There are also other related issues with some examples and relevant discussions about this topic: https://github.com/w3c/csswg-drafts/issues/1039 https://github.com/w3c/csswg-drafts/issues/1409 Bug: 704713 Change-Id: I817b16eb43aa76f4827deb8f1f20efb7fde3dc22 Reviewed-on: https://chromium-review.googlesource.com/923261 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by: Sergio Villar <svillar@igalia.com> Cr-Commit-Position: refs/heads/master@{#562406} 31 May 2018, 23:22:05 UTC
f686741 Chris Nardi 31 May 2018, 23:15:26 UTC Remove tests for the crop property (#10556) There is a comment in the test that it wasn't implemented in anywhere, and it seems to have been removed from the spec (per https://github.com/w3c/csswg-drafts/commit/7f3fb42152f3110f5581901797f6d34c9300cf4b). Remove the reference to the property from the testcases. 31 May 2018, 23:15:26 UTC
c410ffb Emilio Cobos Álvarez 30 May 2018, 08:25:14 UTC Make element-backed pseudos inherit from NAC subtree roots and other NAC inherit from their parents. Currently, NAC always inherits from the closest non-NAC ancestor element, regardless of whether it is for an element-backed pseudo or not. This patch changes the inheritance so that for element-backed pseudos, we inherit from the closest native anonymous root's parent, and for other NAC we inherit from the parent. This prevents the following two issues and allows us to remove the NODE_IS_NATIVE_ANONYMOUS flag: * Avoiding inheriting from the non-NAC ancestor in XBL bindings bound to NAC. - This is no longer a problem since we apply the rule only if we're a pseudo-element, and all pseudo-elements are in native anonymous subtrees. - This also allows to remove the hack that propagates the NODE_IS_NATIVE_ANONYMOUS flag from the ::cue pseudo-element from BindToTree. * Inheriting from the wrong thing if we're a nested NAC subtree. - We no longer look past our NAC subtree, with the exception of ::-moz-number-text's pseudo-elements, for which we do want to propagate ::placeholder to. A few rules from forms.css have been modified because they're useless or needed to propagate stuff to the anonymous form control in input[type="number"] which previously inherited from the input itself. bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1460382 gecko-commit: bbb045179d4f1e45f7001a157171bdca1d0f1901 gecko-integration-branch: mozilla-inbound gecko-reviewers: heycam 31 May 2018, 22:50:36 UTC
3d6920b Fadi Meawad 31 May 2018, 19:20:02 UTC [PageLifecycle] Add WPT test for lifecycle's onfreeze callback Since the onfreeze callback is invoked based on an internal decision from the browser, to be able to test the callback, we are adding support for it from chromeGPUBenchmak as well as in chromedriver/WebDriver. This CL focuses on the chromeGPUBenchmark solution. The WPT test itself, verifies that the onfreeze callback is called, and it also verifies that only fetch keepalive is allowed from withing the callback. Bug: chromium:837709 Change-Id: Ia4cb16dc10625f478ec270617da1a26395a9d29d Reviewed-on: https://chromium-review.googlesource.com/1072899 Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org> Reviewed-by: Shubhie Panicker <panicker@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Commit-Queue: Fadi Meawad <fmeawad@chromium.org> Cr-Commit-Position: refs/heads/master@{#563338} 31 May 2018, 19:30:12 UTC
f172b83 Victor Costan 31 May 2018, 18:22:39 UTC Merge pull request #11281 from csnardi/cookie-store-idl Allow cookie-store IDL test to run even if objects not defined 31 May 2018, 18:22:39 UTC
57fea79 Frédéric Wang 31 May 2018, 17:54:39 UTC WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186127 (#11279) 31 May 2018, 17:54:39 UTC
296a9b3 Chris Nardi 31 May 2018, 17:16:55 UTC Allow cookie-store IDL test to run even if objects not defined By quoting the object constructors/references, we prevent the test from erroring out prior to running and instead allow all of the tests to run. This means that if an implementation only defines one interface but not the other, it will make sure there is test coverage of that interface without having to implement the other. 31 May 2018, 17:16:55 UTC
fe4769e Simon Pieters 31 May 2018, 11:53:55 UTC [css-properties-values-api] Avoid uncaught exception for CSS.registerProperty() 31 May 2018, 16:03:21 UTC
8c8238c Ian Kilpatrick 31 May 2018, 15:23:14 UTC [css-layout-api] Allow passing of serialized data between parent<->child. This allow arbitary parent<->child communation during layout. A parent can send data to a child via: // parent const fragment = yield child.layoutNextFragment({data}); // child *layout(children, edges, constraints, style) { const data = constraints.data; // receive data. } And child to parent via: // child *layout() { return {data}; } // parent const fragment = yield child.layoutNextFragment(); const data = fragment.data; // receive data. As the parent and child layouts may be invoked in different worklet global scopes, and don't allow data shared, the serialization of data uses "kForStorage" which means that SharedArrayBuffers aren't allowed in the serialization. Serialization also occurs so that we are able to cache results. Bug: 726125 Change-Id: Ib7e81b5778cef3af2c2f8a1ccef749f1d2ba4dfa Reviewed-on: https://chromium-review.googlesource.com/1072150 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#563235} 31 May 2018, 15:43:17 UTC
2ae39a0 Chris Nardi 31 May 2018, 15:18:57 UTC Move HTML from untested IDL to a dependency IDL for DOM The DOM idlharness test would not run as dependencies for the HTML IDL file were not declared. However, we don't need to define HTML as untested IDL -- using the new dependency IDL feature generates the same tests but prevents the current dependency problem. 31 May 2018, 15:30:58 UTC
89dc776 Ms2ger 31 May 2018, 14:07:52 UTC HTML: Test hidden attribute on table elements (#11264) 31 May 2018, 14:07:52 UTC
back to top