screen-orientation

edit

WPT coverage of the tests of screen-orientation at the revision 5602b0f210e3. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features) and the reftests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable1315087%
Tentative000–
Reftests000–
All1315087%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • TEST BUG: 2

Stable tests

TestResultSubtestsKindDescription
active-lock.htmlPass3 / 3
event-before-promise.htmlPass1 / 1
fullscreen-interactions.htmlFail1 / 2TEST BUGthe second subtest expects the lock request of an iframe to be rejected with a SecurityError when the page exits fullscreen (the error of Chromium, whose lock requires fullscreen): exiting fullscreen runs the fully unlock the screen orientation steps (https://w3c.github.io/screen-orientation/#interaction-with-fullscreen-api), which reject the pending lock requests of the documents of the tab with an AbortError
hidden_document.htmlError3 / 4TEST BUGthe cleanup of the third subtest calls screen.orientation.unlock() while the document is still hidden (the cleanup that restores the window is asynchronous and runs concurrently): the common safety checks throw a SecurityError for a hidden document (https://w3c.github.io/screen-orientation/#dfn-common-safety-checks), so the harness reports an error and the last subtest does not run
idlharness.window.jsPass25 / 25
lock-bad-argument.htmlPass2 / 2
lock-basic.htmlPass3 / 3
lock-sandboxed-iframe.htmlPass2 / 2
lock-unlock-check.htmlPass2 / 2
nested-documents.htmlPass2 / 2
non-fully-active.htmlPass3 / 3
onchange-event-subframe.htmlPass2 / 2
onchange-event.htmlPass2 / 2
orientation-reading.htmlPass6 / 6
unlock.htmlPass5 / 5