tree: 3bbb6c719a8bd0adaad0f18f1ab5f7d70e2cfdaf [path history] [tgz]
  1. cancel-watch-availability-expected.txt
  2. cancel-watch-availability.html
  3. disable-remote-playback-cancel-watch-availability-throws-expected.txt
  4. disable-remote-playback-cancel-watch-availability-throws.html
  5. disable-remote-playback-prompt-throws-expected.txt
  6. disable-remote-playback-prompt-throws.html
  7. disable-remote-playback-watch-availability-throws-expected.txt
  8. disable-remote-playback-watch-availability-throws.html
  9. idlharness.window-expected.txt
  10. idlharness.window.html
  11. idlharness.window.js
  12. META.yml
  13. README.md
  14. w3c-import.log
  15. watch-availability-initial-callback-expected.txt
  16. watch-availability-initial-callback.html
LayoutTests/imported/w3c/web-platform-tests/remote-playback/README.md

Remote Playback API specification Tests

The Remote Playback API can be found here:

GitHub repository: https://github.com/w3c/remote-playback/

File an issue: https://github.com/w3c/remote-playback/issues/new

Hardware/network dependency

The Remote Playback API requires to communicate with a device over the network. Some behavior would require a real devices to be implemented. In order to keep these tests automated, only behaviors that can be run without user gesture or specific configurations are available here.