| commit | 693401ad169e16217306287d499e592ee4bdfe29 | [log] [tgz] |
|---|---|---|
| author | James Graham <james@hoppipolla.co.uk> | Fri Feb 25 18:28:34 2022 |
| committer | moz-wptsync-bot <wptsync@mozilla.com> | Sat Feb 26 10:00:11 2022 |
| tree | dc168a6a14eac087fd6f4119e4b197382d024a64 | |
| parent | d057b2ffa350290a4831080b29c81d2cc701ea10 [diff] |
Make marionette events use EventUtil.js directly Rather than copying over the code from EventUtils, load EventUtils.js into event.js. This is slightly complicated by the fact that EventUtils.js depends on the existence of a global named `window`. So instead of loading the script as a normal component, we need to use `loadSubScript` to create an instance of the script with the required window binding (this is similar to the approach the CDP module uses). The actual API changes for mouse events are ~trivial, but for key events things are a little more involved. The code previously (in effect) called synthesizeKey with the virtual keycode as the aKey argument. However EventUtils.js documents this as deprecated, so we switch to providing the actual key, with the `KEY_` prefix for non-printable characters. To make this easier, all the data about various keys from the WebDriver spec is collapsed into a single lookup table, rather than having a table for each interesting property. Differential Revision: https://phabricator.services.mozilla.com/D138449 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1686666 gecko-commit: b609cc1c05e7108ed02ed97d037bc581b47cfa29 gecko-reviewers: webdriver-reviewers, whimboo
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!