clear-site-data
editWPT coverage of the tests of clear-site-data 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 | 12 | 13 | 0 | 92% |
| Tentative | 2 | 2 | 0 | 100% |
| Reftests | 0 | 0 | 0 | – |
| Crash tests | 0 | 0 | 0 | – |
| All | 14 | 15 | 0 | 93% |
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: 1
Stable tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
clear-cache-bfcache.https.html | Pass | 4 / 4 | ||
clear-cache.https.html | Pass | 13 / 13 | ||
executionContexts.sub.html | Pass | 2 / 2 | ||
navigation-insecure.html | Pass | 4 / 4 | ||
navigation.https.html | Pass | 4 / 4 | ||
no-cors-fetch-iframe.https.sub.html | Pass | 1 / 1 | ||
no-cors-fetch-window.https.sub.html | Pass | 1 / 1 | ||
resource.html | Timeout | 2 / 4 | TEST BUG | the http resource on a https page subtest: the https iframe navigates itself to the http: URL of send_report.html, which is blocked as mixed content (the navigation of a child navigable from a document whose origin is potentially trustworthy, https://w3c.github.io/webappsec-mixed-content/#should-block-fetch), so the report is never posted and the test times out |
set-cookie-after-clear-all.https.html | Pass | 1 / 1 | ||
set-cookie-after-clear-cookies.https.html | Pass | 1 / 1 | ||
set-cookie-before-clear-all.https.html | Pass | 1 / 1 | ||
set-cookie-before-clear-cookies.https.html | Pass | 1 / 1 | ||
storage.https.html | Pass | 9 / 9 |
Tentative tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
clear-cache-bfcache-partitioning.tentative.https.html | Pass | 2 / 2 | ||
clear-cache-partitioning.tentative.https.html | Pass | 10 / 10 |