Intent to Ship: Clear BFCache during browsing data removal
Mingyu Lei
Contact emails
le...@chromium.org, fer...@chromium.orgExplainer
NoneSpecification
NoneSummary
When performing browsing data removal (e.g. via chrome://settings/clearBrowserData, hard reload, or the `Clear-Site-Data ` header), the disk and in-memory cache for the HTTP response will be cleared. In addition to this, if the browsing data removal's data type is "cache", then all the BFCache entries matching the origin will be cleared as well.
Blink component
UI>Browser>Navigation>BFCacheSearch tags
bfcacheTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
None
Gecko: N/A (https://bugzilla.mozilla.org/show_bug.cgi?id=1671182) Firefox has removed the cache type data removal for Clear-Site-Data header.
WebKit: Shipped/Shipping (https://github.com/WebKit/WebKit/pull/4617)
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
NoIs this feature fully tested by web-platform-tests?
NoFlag name on chrome://flags
NoneFinch feature name
NoneNon-finch justification
The feature has already been released.
Requires code in //chrome?
FalseTracking bug
https://crbug.com/1428640Estimated milestones
| Shipping on desktop | 115 |
| Shipping on Android | 115 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
https://github.com/w3c/webappsec-clear-site-data/issues/73Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5096684790480896
Mike Taylor
On 8/1/23 7:54 AM, 'Mingyu Lei' via blink-dev wrote:
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN_fHtn%3DJ5E7Hdcpv9Ojyhrf0AUdoL3PY%3DJxq7jByp5O5pPNgw%40mail.gmail.com.
Fergal Daly
Fergal Daly
On 8/1/23 7:54 AM, 'Mingyu Lei' via blink-dev wrote:
Given that WebKit is shipping this and we would like to, any reason to not document this behavior to the Clear-Site-Data spec?
Daniel Bratell
Ex post facto LGTM1
Just try to get that spec updated so that developers will know what to expect.
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAozHLk7H%2BeZS3WH4ZuicW3oDsadWTg6CYc_0pFXhM7aJdxU5w%40mail.gmail.com.
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5f493d03-bd3c-6e93-8d5f-d7e7c9ac8821%40gmail.com.
Mike Taylor
LGTM3