880870 - When the low storage limit is hit, the data written to local storage should be rolled back, not kept

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Jason Smith [:jsmith]]

Build: 6/5/2013 1.01
Device: Ikura

STR

1. Put the device down to 5.9 MB of device storage
2. Go to http://jds2501.github.io/webapi-permissions-tests/largelocalstorage.html in the browser
3. Check the device storage size

Expected

We should receive a low storage warning and the data written to local storage should be rolled back, not kept.

Actual

The low storage warning is received, but the data was requested to be written to for local storage is still written. This means that the user's device storage can go below the 5 MB threshold. In my test case, I'll end up at 4.2 MB as a result.

Note that this is differing behavior from what we do with appcache. With appcache, you will fail to write those appcache resources when the 5 MB limit is reached and you'll rollback the changes. I think we should do the same with local storage.

Comment 1

[Jason Smith [:jsmith]]

Not a blocker because we do give clear notification to the user that they are on low storage. We should try to fix this eventually however, as the rollback ensures that we don't put our storage below the 5 MB critical limit.

Comment 2

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.