#1091: Add prefetchCache and prerenderCache to Clear-Site-Data header
Discussions
Log in to see TAG-private discussions.
Discussed
May 19, 2025 (See Github)
Martin: I think we can say "thanks for coming" on this. It's just maintenance. We may as well say it's ok.
Torgo: where is it going? positive feedback from other implementers?
Martin: it does from Mozilla, I think
Jeffrey: yes, simon has replied. There is one concern that clearsitedata doesn't have a place to land.
Martin: so one way to do that is simply say in your own spec, this is it. the prefetch specs could modify the clearsite stuff.
Jeffrey: I guess the other concern is that the new spec is just in the WICG.
Discussed
May 19, 2025 (See Github)
Martin: I think we can say "thanks for coming" on this. It's just maintenance. We may as well say it's ok.
Torgo: where is it going? positive feedback from other implementers?
Martin: it does from Mozilla, I think
Jeffrey: yes, simon has replied. There is one concern that clearsitedata doesn't have a place to land.
Martin: so one way to do that is simply say in your own spec, this is it. the prefetch specs could modify the clearsite stuff.
Jeffrey: I guess the other concern is that the new spec is just in the WICG.
OpenedMay 12, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of the feature for adding prefetchCache and prerenderCache values to Clear-Site-Data header.
We propose adding two new values to the Clear-Site-Data header to help developers target clearing the prerender and prefetch cache: prefetchCache and prerenderCache.
Further details: