commit | e6af52414f6138627f0c948d0662bc3a05f9ab13 | [log] [tgz] |
---|---|---|
author | Masayuki Nakano <masayuki@d-toybox.com> | Mon Jul 25 07:06:38 2022 |
committer | moz-wptsync-bot <wptsync@mozilla.com> | Mon Jul 25 10:06:45 2022 |
tree | cfaae94a36c957c95dffbdca0f391a097ca1ab69 | |
parent | 3aadc8d84891c1f5018a5684def72021a44ecea1 [diff] |
Add tentative WPT for checking the handling of `insertParagraph` in elements outside <body I think that these edge cases are not reasonable for any web apps, but browsers need to take care for avoiding odd result including crash. I believe that the simplest approach is, elements which are children of `<html>` or `<head>` should be treated like as `<body>` which is never unwrapped nor joined with the other elements. However, the behavior is incompatible with browsers, so doing it may break existing web apps. Therefore, I think that the reasonable approach is, browsers should split normal elements which is usually visible and appear in `<body>` should be split even if they are outside the `<body>`. However, some special elements such as `<style>` and `<script>` which may be appear in `<head>` but usually invisible and affects entire the document should not be split. The following patch adds delete/join cases. Differential Revision: https://phabricator.services.mozilla.com/D152381 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1777904 gecko-commit: 0c0cf642957c1d5947ab5bf3d1df63ef5d0488b8 gecko-reviewers: m_kato
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!