|No way to test 'QuotaExceededError'|
|Reported by a...@scirra.com, Mar 30||Back to list|
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: We recently launched a large PWA at editor.construct.net. Some users are reporting it crashes with "QuotaExceededError". Presumably they don't have much disk space or something like that, but obviously this shouldn't crash the app and should be handled elegantly. However it's not clear how to develop this feature. What is the expected behavior? Dev tools should have a way to set the available storage quota to something very low like 1kb. Then we can simply try testing our app and see real QuotaExceededError exceptions and make sure they don't bring down the whole app. What went wrong? No idea what to do to fix these exceptions. Did this work before? No Chrome version: 57.0.2987.133 Channel: stable OS Version: 10.0 Flash Version:
Reporter@ Could you please help us by providing sample crash ID's from chrome://crashes for further investigation. Thanks!
Thank you for providing more feedback. Adding requester "email@example.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
|► Sign in to add a comment|