tree: e629a3ecca6fce4283247e89f27fdb07cf8afcb2 [path history] [tgz]
  1. ar/
  2. resources/
  3. events_deviceconnect.https.html
  4. navigator_xr_detached.https.html
  5. navigator_xr_early_detached.https.html
  6. README.md
  7. render_state_vertical_fov_inline.https.html
  8. xr_view_projection_detached.https.html
  9. xrDevice_supportsSession_immersive.https.html
  10. xrDevice_supportsSession_immersive_unsupported.https.html
  11. xrDevice_supportsSession_non_immersive.https.html
  12. xrFrame_getPose.https.html
  13. xrSession_dataProviderDisconnect_immersive.https.html
  14. xrSession_dataProviderDisconnect_inline.https.html
  15. xrSession_environmentBlendMode.https.html
  16. xrSession_environmentProviderDisconnect.https.html
  17. xrSession_framesThrottled.https.html
  18. xrWebGLLayer_dirty_framebuffer.https.html
chromium/src/third_party/blink/web_tests/wpt_internal/webxr/README.md

WebXR Internal Tests

In keeping with the requirements for the wpt_internal tests, these tests validate behavior that is not yet in a stable version of the spec (e.g. AR), test Chrome specific constants, or test things specific to the blink/mojom implementations.

In order to reference xr-internal-device-mocking.js (or other additional files that may be required for an internal test), the additionalChromiumResources variable/array should be set before including webxr_util.js, as webxr_util.js begins loading resources immediately.

To port a test from wpt_internal to external/wpt, the “/webxr/resources/...” paths will need to be converted to “resources/...” paths, and any reliance on internal APIs (i.e. any usage of additionalChromiumResources) should be removed. Those should be the only changes required other than those required by wpt lint.

For more details, please reference the wpt_internal [README] WPT Readme.