Feature description: Add usage details to the result of storageManager.estimate()
Eng owner: jarrydg@chromium.org
Product owner: jarrydg@chromium.org
Design doc:
Are you planning on experimenting before launch? TBD
Any new strings?
Any implications for Google webservices (i.e. sync, translate)?
Binary size?
Do the existing perf tests exercise all aspects of your new feature(s)?
There have been frequent requests from users of `navigator.storage.estimate()` to provide a per storage type breakdown estimation. Currently, a call to this function yields only an estimate of the quota usage for all storage systems combined, making it difficult to reason about what is using up quota.
Feature description: Add usage details to the result of storageManager.estimate()
Eng owner: jarrydg@chromium.org
Product owner: jarrydg@chromium.org
Design doc:
Are you planning on experimenting before launch? TBD
Any new strings?
Any implications for Google webservices (i.e. sync, translate)?
Binary size?
Do the existing perf tests exercise all aspects of your new feature(s)?
There have been frequent requests from users of `navigator.storage.estimate()` to provide a per storage type breakdown estimation. Currently, a call to this function yields only an estimate of the quota usage for all storage systems combined, making it difficult to reason about what is using up quota.
Ongoing discussion regarding this change: https://github.com/whatwg/storage/issues/63
Feature description: Add usage details to the result of storageManager.estimate()
Eng owner: jarrydg@chromium.org
Product owner: jarrydg@chromium.org
There have been frequent requests from users of `navigator.storage.estimate()` to provide a per storage type breakdown estimation. Currently, a call to this function yields only an estimate of the quota usage for all storage systems combined, making it difficult to reason about what is using up quota.
Ongoing discussion regarding this change: https://github.com/whatwg/storage/issues/63
Comment 1 by jarrydg@chromium.org
, Nov 12