notifications
editWPT coverage of the tests of notifications at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.
| Group | Passing | Tests | Disabled | Pass rate |
|---|---|---|---|---|
| Stable | 19 | 21 | 1 | 95% |
| Tentative | 3 | 4 | 0 | 75% |
| Reftests | 0 | 0 | 0 | – |
| Crash tests | 2 | 2 | 0 | 100% |
| All | 24 | 27 | 1 | 92% |
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
- NOT IMPLEMENTED: 1
Stable tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
constructor-basic.https.html | Pass | 4 / 4 | ||
constructor-invalid.https.html | Pass | 1 / 1 | ||
constructor-non-secure.html | Pass | 1 / 1 | ||
event-onclose.https.html | Pass | 2 / 2 | ||
event-onshow.https.html | Pass | 1 / 1 | ||
fetch-url-resolve.https.window.js | Pass | 2 / 2 | ||
getnotifications-across-processes.https.window.js | Pass | 3 / 3 | ||
historical.any.js | Pass | 4 / 4 | ||
icon-fetch-blob-url.https.window.js | Pass | 8 / 8 | ||
icon-url-encoding-euc-kr.https.html | Pass | 1 / 1 | ||
idlharness.https.any.js | Pass | 243 / 243 | ||
instance.https.window.js | Timeout | 11 / 34 | TEST BUG | the window subtests construct a Notification with actions, which the constructor rejects with a TypeError (only the persistent notifications have actions); the notificationclose subtests of the service worker wait for a notificationclose event after close(), which the specification only fires when the user closes a persistent notification (the test notes that it times out in Blink and Gecko) |
lang.https.html | Pass | 37 / 37 | ||
permission.html | Pass | 1 / 1 | ||
permissions-non-secure.html | Pass | 3 / 3 | ||
registration-association.https.window.js | Disabled | – | TEST BUG | prepareActiveServiceWorker() awaits navigator.serviceWorker.ready, which is resolved once per container (https://w3c.github.io/ServiceWorker/#navigator-service-worker-ready): in the first subtest it is already resolved with the registration of the setup, so it does not wait for the new registration to be activated. The second subtest calls showNotification() on the new registration, which rejects with a TypeError while its active worker is null (https://notifications.spec.whatwg.org/#dom-serviceworkerregistration-shownotification), so the result depends on whether the activation ended first (it failed 2 runs of 5 locally) |
shownotification-window.https.html | Pass | 1 / 1 | ||
shownotification-without-permission.https.window.js | Pass | 1 / 1 | ||
shownotification.https.window.js | Pass | 11 / 11 | ||
tag.https.html | Pass | 2 / 2 | ||
worker-gc.https.window.js | Pass | 1 / 1 |
Tentative tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
cross-origin-nested.tentative.https.sub.html | Pass | 4 / 4 | ||
cross-origin-same-site-request.tentative.https.sub.html | Pass | 1 / 1 | ||
cross-origin-serviceworker.tentative.https.sub.html | Pass | 1 / 1 | ||
icon-fetch.tentative.https.window.js | Timeout | 0 / 1 | NOT IMPLEMENTED | the fetch steps of the notifications: the library does not display the notifications, so it does not fetch their icon, image and badge (the host fetches them if it displays them) |
Crash tests
| Test | Result | Variants | Kind | Description |
|---|---|---|---|---|
crashtests/show-and-close.https.html | Pass | 1 / 1 | ||
global-teardown-crash.html | Pass | 1 / 1 |