Re: [whatwg/storage] Define the behavior when calling persist() if the resource has been already used (#25)

Maybe I don't understand the issue being raised in the OP?

> When can UA resolve promise after calling persist() if other tabs already accessed the resource? It's possible that other tabs hold the storage resources. Can the specification suggest how to deal with this situation?

I don't see a problem with an IndexedDB being opened and in use while the persistent attribute is being modified. The attribute only affects whether the user-agent is required to get user consent prior to clearing the origin's resources. The attribute applies to all existing and future resources in the box, regardless of whether an existing resource is currently in use. Where's the problem?

I think how to handle concurrent calls to persist() from multiple pages is more interesting implementation detail.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/storage/issues/25#issuecomment-215256373