commit | 1854f413a8e040d191d94b3af819fd0af35b4ca7 | [log] [tgz] |
---|---|---|
author | Masayuki Nakano <masayuki@d-toybox.com> | Tue Oct 12 03:18:25 2021 |
committer | moz-wptsync-bot <wptsync@mozilla.com> | Tue Oct 12 13:20:34 2021 |
tree | 6ca3825b9b87d1e68123a12a623151a53b571736 | |
parent | 7a11185ba72730bcca63cc7b1bb1942a5f094228 [diff] |
Add `nsINode::IsInDesignMode()` to check whether the node is directly in design mode There are a lot of check of `Document`'s editable state **with** comments. This means that it's unclear for developers that only `Document` node is editable in design mode. Additionally, there are some points which use composed document rather than uncomposed document even though the raw API uses uncomposed document. Comparing with the other browsers, checking uncomposed document is compatible behavior, i.e., nodes in shadow trees are not editable unless `contenteditable`. Therefore, `nsINode` should have a method to check whether it's in design mode or not. Note that it may be called with a node in UA widget. Therefore, this patch adds new checks if it's in UA widget subtree or native anonymous subtree, checking whether it's in design mode with its host. Differential Revision: https://phabricator.services.mozilla.com/D126764 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1732845 gecko-commit: 680ebfd6ee371e885e294af566f81e5bf17df6c0 gecko-reviewers: smaug
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!