#1065: Update QuotaExceededError to a DOMException derived interface
Discussions
Comment by @jyasskin Apr 28, 2025 (See Github)
This looks simple enough that we don't need to review it, given that it's proceeding in an appropriate group. We did note that the "Mozilla comments" link should really go to their standards-positions repo, or at the very least a comment by a Mozillan stating a clear opinion on Mozilla's behalf.
OpenedMar 6, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of an updated QuotaExceededError interface.
Currently, when the web platform wants to tell you when you've exceeded quota, it will use
DOMException
with the specificname
property set toQuotaExceededError
. However this does not allow carrying additional information.This proposes removing "QuotaExceededError" from the list of built-in
DOMException
names, and instead creates a class nameQuotaExceededError
from the list of built-inDOMException
and has the additional optional propertiesquota
andrequested
. We propose all instances of specs that throw "QuotaExceededError"DOMException
s get upgraded to instead throwQuotaExceededError
s. For now, such specs would leave thequota
andrequested
properties at their default value ofnull
, but they could eventually upgrade to include that data, if it's useful for their use case (and isn't, e.g., a privacy leak).Further details: