commit | 3b12e5fda679a5965a108fda31c170e4e2681018 | [log] [tgz] |
---|---|---|
author | Masayuki Nakano <masayuki@d-toybox.com> | Sat Mar 18 12:25:01 2023 |
committer | moz-wptsync-bot <wptsync@mozilla.com> | Sun Mar 19 09:43:23 2023 |
tree | ce22e4d43760d10df6893fb7aefc2374c63bfa8f | |
parent | 2bf9cc74a8b58bb0af9ae9d31f9919e8a3b56205 [diff] |
part 1: Make `nsIFrame::GetFrameFromDirection` treat frames in different native anonymous subtree not selectable It's called by `PeekOffsetFor*` and `GetPrevNextBidiLevels`, so it's used for considering whether to put caret or move a selection range boundary. Therefore, it should treat nodes which can be managed by `Selection` as selectable. In theory, even if a native anonymous subtree does not have an independent selection, its content nodes should not be the container of the selection range boundaries of selection outside the subtree since Selection API shouldn't expose nodes in native anonymous subtrees. Therefore, it can simply treat content nodes in different anonymous subtrees are not selectable. Note that it's not standardized that how `Selection.modify` works with various content nodes. https://w3c.github.io/selection-api/#dom-selection-modify And also Chrome cannot cross generated content like form controls with this API. This could cause web-compat issues, but it does not make sense for caret navigation, and anyway out of scope of this bug. Therefore, this patch just adds the crash test. Differential Revision: https://phabricator.services.mozilla.com/D172204 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1384606 gecko-commit: 1da78b4706832a106b8b61c1f2de6dea4c4bee01 gecko-reviewers: emilio
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!