Re: [w3c/IndexedDB] Specify the exception for read failures arising due to partial data loss on the file system (Issue #423) from Andrew Sutherland on 2024-09-23 (public-webapps-github@w3.org from September 2024)

From: Andrew Sutherland <notifications@github.com>
Date: Mon, 23 Sep 2024 15:45:24 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/423/2369677614@github.com>

I agree that it's worth standardizing the error for cases where it's reported, and [`NotReadableError`](https://webidl.spec.whatwg.org/#notreadableerror) seems appropriately descriptive.

That said, it's been our belief in Firefox that unless we spec some kind of content opt-in to avoid the behavior, data corruption should result in the containing storage bucket being cleared.  [Multiple storage buckets](https://github.com/WICG/storage-buckets) seems like the most practical approach since it normalizes a hopefully uncommon case (data corruption) into a common case that code should already be handling (data clearing due to storage pressure).

Related discussions: [Storage corruption reporting](https://github.com/whatwg/storage/issues/75).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/423#issuecomment-2369677614
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/423/2369677614@github.com>

Received on Monday, 23 September 2024 22:45:28 UTC