commit | a4288b9d453a8c48078b3e93a58c86cf97ac3551 | [log] [tgz] |
---|---|---|
author | L. David Baron <dbaron@chromium.org> | Wed Oct 04 19:14:28 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Oct 04 19:32:04 2023 |
tree | 24040f525f1af6294fdbff8c9568a15e10fdaa9b | |
parent | 507f74f14524f1719efdc92f9723e78898119234 [diff] |
Update mutation event suppression for <details name> to revised spec rules. The rules for mutation event suppression for <details name> were revised during the process of reviewing the spec PR, based on the discussion starting at https://github.com/whatwg/html/pull/9400#discussion_r1340856291 . The updated spec says that mutation events are suppressed during the "ensure details exclusivity by closing other elements if needed" and "ensure details exclusivity by closing the given element if needed" algorithms. This updates the implementation and tests to follow that rule. (The "handling of insertion of elements into group" test is testing the case where the events were already suppressed.) This also renames the test to remove "tentative" from the name, since the spec PR is landed and the test is now (with this change) up-to-date with the spec. Bug: 1444057 Change-Id: I9078beeb3527f2515f6e10efbf93a94232221238 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4912273 Commit-Queue: David Baron <dbaron@chromium.org> Reviewed-by: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1205367}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!