Bug 22370 - Inform script of corruption-induced data loss
Summary: Inform script of corruption-induced data loss
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2013-06-14 22:34 UTC by dgrogan
Modified: 2015-08-10 20:10 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description dgrogan 2013-06-14 22:34:57 UTC
It would be nice to be able to notify script that some data may have been lost due to disk corruption or other failure.

This was discussed some in [thread], with the leading idea being an attribute on the upgradeneeded and success events that are fired at open requests. The attribute's could be called "dataLoss" with values including "none", "total", or "partial".

The chrome implementation has been started, see [chromebug].

[thread] http://lists.w3.org/Archives/Public/public-webapps/2013JanMar/0355.html
[chromebug] https://code.google.com/p/chromium/issues/detail?id=172626
Comment 1 dgrogan 2013-06-14 22:35:39 UTC
Marking RESOLVED LATER to denote that it should be considered for V2, not V1.
Comment 2 dgrogan 2013-10-31 17:29:32 UTC
We have heard from web application developers that they want even more transparency into what is causing data loss. Chrome is going to ship a dataLossMessage alongside dataLoss on the upgradeneeded event, as described in this thread:

Comment 3 Joshua Bell 2015-04-23 15:56:26 UTC
As dgrogan@ noted, we shipped IDBVersionChangeEvent#dataLoss and IDBVersionChangeEvent#dataLossMessage in Chrome, and it's seeing use. Since they're not widely publicized entry points we're open to alternate suggestions.
Comment 4 Joshua Bell 2015-08-10 20:10:54 UTC
Moved to https://github.com/w3c/IndexedDB/issues/30