| commit | b3bc25e2e6ea65309c1229d3100d2f41e8dd2a3b | [log] [tgz] |
|---|---|---|
| author | Masayuki Nakano <masayuki@d-toybox.com> | Tue Oct 10 03:24:37 2023 |
| committer | moz-wptsync-bot <wptsync@mozilla.com> | Tue Oct 10 10:15:06 2023 |
| tree | 4e03517f46e5c239a260ccf67ad02122db5ee772 | |
| parent | bcd57c07cd014003f58d693e63a5d0dfe39fb57c [diff] |
Make `nsIFrame::HandleEvent` move caret when secondary mouse button down The other browsers move focus and `Selection` whe right click even if the clicked element is not editable and even if there is a non-collapsed selection. Fortunately, we already have similar code for the middle button press. Therefore, we can make it run when the pressed button is the secondary button. This also fixes bug 416546 and does not resurrect bug 709476. However, this patch adds 2 prefs for making users customizable. Our traditional behavior is, we never collapse non-collapses selection with a right click even if clicked outside the selection. This allows users to open context menu for selected text much easier. Therefore, even though the behavior is different from the others, we should keep the traditional behavior, but some users may want the other browsers' behavior instead. For them, this should be switchable by a pref. Additionally, I'm still not sure collapsing selection with a right click in non-editable content especially for users using the caret browsing mode. Therefore, for making things safer, this adds a pref to disable the new behavior in the non-editable content. Differential Revision: https://phabricator.services.mozilla.com/D189991 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1845241 gecko-commit: 81712ea026098ff0a4d5739d4deae97fcb21f296 gecko-reviewers: edgar, emilio, dom-core
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!