- From: <bugzilla@jessica.w3.org>
- Date: Sat, 06 Nov 2010 09:34:43 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11247 Summary: 7.1.3.4: I think it would be a good practice to throw a QUOTA_EXCEEDED_EXCEPTION just some seconds (i.e. 5s) BEFORE the QUOTA_EXCEEDED_ERR is thrown. This would give us a way to convict the script/data in a clean state with(out) or at least less corrupted Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#web appapis OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Specification: http://www.whatwg.org/specs/web-apps/current-work/ Section: http://www.whatwg.org/specs/web-apps/current-work/#webappapis Comment: 7.1.3.4: I think it would be a good practice to throw a QUOTA_EXCEEDED_EXCEPTION just some seconds (i.e. 5s) BEFORE the QUOTA_EXCEEDED_ERR is thrown. This would give us a way to convict the script/data in a clean state with(out) or at least less corrupted data. The QUOTA_EXCEEDED_EXCEPTION-object should contain a duration (in millis), which tells us how long our cleanup could take at max, before our procedures may be killed with the QUOTA_EXCEEDED_ERR or after the user prompt (which imho also should throw an exception, if the user tells the browser to stop). Posted from: 92.75.155.123 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Saturday, 6 November 2010 09:34:45 UTC