- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 27 Sep 2019 06:36:48 -0700
- To: whatwg/storage <storage@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 27 September 2019 13:37:10 UTC
Given the use cases discussed reporting could work, but might be less useful than directly exposing it (and exposing control over it). 1. The application would not know which user's storage is corrupted. 2. The application would not be able to decide whether to clear the storage or keep it somehow for investigation. Reporting could work for the case where you navigate to a document whose origin has corrupted storage, but that only gives you a fairly high-level signal. -- 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/74#issuecomment-535942459
Received on Friday, 27 September 2019 13:37:10 UTC