is-input-pending
editWPT coverage of the tests of is-input-pending 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.
| Group | Passing | Tests | Disabled | Pass rate |
|---|---|---|---|---|
| Stable | 10 | 10 | 0 | 100% |
| Tentative | 0 | 2 | 0 | 0% |
| Reftests | 0 | 0 | 0 | – |
| All | 10 | 12 | 0 | 83% |
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 RUNNER: 2
Stable tests
Tentative tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
tentative/same-origin-subframe.sub.html | Fail | 0 / 2 | TEST RUNNER | the test driver dispatches the input of test_driver.Actions from timers of the event loop, and the runner does not report these pending actions to isInputPending() (BrowsingContextOptions.PendingInput is not set, so it returns false); the security tests, which expect false, pass |
tentative/toplevel.html | Fail | 0 / 1 | TEST RUNNER | the test driver dispatches the input of test_driver.Actions from timers of the event loop, and the runner does not report these pending actions to isInputPending() (BrowsingContextOptions.PendingInput is not set, so it returns false); the security tests, which expect false, pass |