7938 2009-10-17 00:22:59 +0000 SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem 2009-10-21 09:09:45 +0000 1 1 1 Unclassified WebAppsWG Web Storage (editor: Ian Hickson) unspecified PC All RESOLVED WONTFIX NE P2 normal --- 1 nikunj.mehta ian ian mike public-webapps public-webapps-bugzilla oldest_to_newest 28424 0 nikunj.mehta 2009-10-17 00:22:59 +0000 In WebDatabase: The user agent may raise a SECURITY_ERR exception instead of returning a Database object if the request violates a policy decision (e.g. if the user agent is configured to not allow the page to open databases). Under setItem(), the Web Storage spec says: # If it couldn't set the new value, the method must raise an # QUOTA_EXCEEDED_ERR exception. (Setting could fail if, e.g., the user has # disabled storage for the site, or if the quota has been exceeded.) Per Jonas [1]: It seems silly to [sic] for *every* feature mention that the UA may do something different if the user has opted to disable a feature for whatever reason. [1] http://www.w3.org/mid/63df84f0909211145y2837d45fpb50f5285f740144c@mail.gmail.com Both cases look similar enough and it feels inappropriate to proliferate error codes for each different situation. Proposal: Use one error code for both. 28696 1 ian 2009-10-21 09:09:45 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: QUOTA_EXCEEDED_ERR makes sense when you're trying to _set_ something, because disabling setting is like making the quota zero. SECURITY_ERR makes sense when _opening_ something, because that's what's used on the platform consistently for that kind of error. I think making these two consistent would be inappropriate.