![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 3 and Version 4 of Ticket #63636, comment 4
- Timestamp:
- 06/30/2025 10:54:32 PM (13 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #63636, comment 4
v3 v4 7 7 }}} 8 8 9 According to MDN, it says it"might" clear out the bfcache "depending on the browser". In testing with Chrome, however, this doesn't seem to work. So the JavaScript-based client-side bfcache invalidation still seems needed.9 According to MDN, it says this "might" clear out the bfcache "depending on the browser". In testing with Chrome, however, this doesn't seem to work. So the JavaScript-based client-side bfcache invalidation still seems needed. 10 10 11 11 This remains an [https://github.com/w3c/webappsec-clear-site-data/issues/73 open question] in w3c/webappsec-clear-site-data. There's another [https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Clear-Site-Data#executioncontexts executionContexts] directive which seems to have been intended for this purpose, but it is not (any longer) [https://caniuse.com/mdn-http_headers_clear-site-data_executioncontexts implemented] by browsers.
