clear-site-data

edit

WPT coverage of the tests of clear-site-data 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	Pass rate
Stable	10	13	77%
Tentative	2	2	100%
Reftests	0	0	–
All	12	15	80%

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
NOT IMPLEMENTED: 2

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`	Fail	0 / 1	NOT IMPLEMENTED	the storage partitioning by top-level site: the local storage of the cross-site iframe is the unpartitioned storage of its origin, which a response loaded in a third-party context does not clear (as `no-cors-fetch-window.https.sub.html` expects); the browsers clear the partitioned storage of the iframe
`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`	Timeout	6 / 8	NOT IMPLEMENTED	the service worker registrations of the origin are unregistered (https://w3c.github.io/webappsec-clear-site-data/#clear-dom-accessible-storage), so the clients that a service worker controls keep it until they are unloaded (https://w3c.github.io/ServiceWorker/#unregister-algorithm); the test expects the behavior of Chromium, which deletes the registrations and removes the controller of the clients at once (`controllerchange`)

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