Update QuotaExceededError to a DOMException derived interface

[ayuishii]

こんにちは 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 specific name property set to QuotaExceededError. 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 name QuotaExceededError from the list of built-in DOMException and has the additional optional properties quota and requested. We propose all instances of specs that throw "QuotaExceededError" DOMExceptions get upgraded to instead throw QuotaExceededErrors. For now, such specs would leave the quota and requested properties at their default value of null, but they could eventually upgrade to include that data, if it's useful for their use case (and isn't, e.g., a privacy ).

• Explainer¹: Upgrade QuotaExceededError to a DOMException derived interface whatwg/webidl#1465
• Specification: Upgrade QuotaExceededError to a DOMException derived interface whatwg/webidl#1465
• WPT Tests: To be added (current DomException WPT here)
• Security and Privacy self-review²: This should not be applicable to this change. While it allows features to allow carrying additional information, it does not require it. It should be evaluated case-by-case to ensure it does not cause any privacy s for that feature.
• repo: https://.com/whatwg/webidl
• Primary contacts:
  • Domenic Denicola(@domenic ), Google, proposal author
  • Ayu Ishii (@ayuishii ), Google
• Organization/project driving the specification: Google
• Multi-stakeholder support³:
  • Chromium comments: Supportive/driving
  • Mozilla comments: Under consideration
  • WebKit comments: Update QuotaExceededError to a DOMException derived interface WebKit/standards-positions#468
• Status/issue trackers for implementations⁴: https://chromestatus.com/feature/6194847180128256

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• The group where the work on this specification is currently being done: WHATWG
• Major unresolved issues with or opposition to this specification: none
• This work is being funded by: Google

[jyasskin]

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.