commit | b2e541f880ab1d03f0ba58b80a05993c43e2a8fc | [log] [tgz] |
---|---|---|
author | Alex Cooper <alcooper@chromium.org> | Thu Dec 19 02:15:10 2019 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Dec 19 02:31:35 2019 |
tree | 3a365f357eed6419c55edab187f596135c548131 | |
parent | 269e7c07aa335a2d36279b2229b351fefbf98a80 [diff] |
Use XRSessionMode where appropriate Refactor XRSessionOptions and XRRuntimeOptions to use an enum, XRSessionMode, where appropriate rather than a pair of bools. As the WebXr spec evolved, the mojom definitions evolved with it. Now that WebVr has been removed and the spec has been solidified, this refactors portions of the mojom to fit better and simplify the code. As a result, a blink-side enum was able to be replaced with this new mojom enum. Unfortunately, a device-side enum was not able to be removed, but it was able to be scoped to just the SessionMetricsHelper. Hopefully future cleanup will enable removal of this enum as well. A couple of changes are worth calling out specifically: Some slight behavior changes were added, which fit with the expectations of the code. Namely, some runtimes that only checked for "immersive", and not "environment_integration", now assert that the request is for "ImmersiveVr", which more closely reflects reality. XrRuntimeManager::GetRuntimeForOptions was also cleaned up from a more complicated set of if-blocks to a switch statement. Fixed: 1035205 Change-Id: I09f39d4a80f1454d5a9aa58fb785169ba5338510 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973156 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Piotr Bialecki <bialpio@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#726205}
The web-platform-tests Project is a W3C-coordinated attempt to build 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:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf 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.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 http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
In the vast majority of cases the only upstream branch that you should need to care about is master
. If you see other branches in the repository, you can generally safely ignore them.
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!