[encrypted-media] Clarify EME persistent data behavior related to `Clear-Site-Data` (#503)

xhwang-chromium has just created a new issue for https://github.com/w3c/encrypted-media:

== Clarify EME persistent data behavior related to `Clear-Site-Data` ==
There are some other W3C specs and proposals managing storage in general. And the EME spec should clarify the behavior of the [Persistent Data](https://www.w3.org/TR/encrypted-media/#persistent-state-requirements) related to those specs.

For example, [Clear-Site-Data](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data) response header is a way for sites to clear data they've previously stored (most common example being on logout). The header can specify different directives, e.g. `cache`, `cookies` or `storage`, where the `storage` directive means to [remove all DOM storage for the origin of the response URL](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data#directives), including  storage mechanisms such as localStorage, IndexedDB, FileSystem API data etc.

Given the `storage` directive includes so many storage mechanisms, the question is whether EME persistent storage should be part of it.

Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/503 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 22 March 2023 16:06:37 UTC