Re: [w3c/IndexedDB] How should commit() failures be surfaced when freezing / unloading (#237) from Joshua Bell on 2019-09-20 (public-webapps-github@w3.org from September 2019)

From: Joshua Bell <notifications@github.com>
Date: Thu, 19 Sep 2019 19:09:47 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/237/533374291@github.com>

**TPAC 2019 Web Apps Indexed DB triage notes:**

We think the ideas in https://github.com/wanderview/storage-corruption-reporting could apply here, if made more general. If a transaction fails for any reason (corruption, I/O error or logic error) then having that available for inspection/reporting by a site would be valuable. This would be done regardless of whether the transaction did manage to fire abort events to script directly. There are issues with how much and for how long the data is retained that need to be sorted out. 



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

Received on Friday, 20 September 2019 02:10:09 UTC