- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 Jun 2014 09:07:05 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25974 Bug ID: 25974 Summary: DOMError removal language could be improved Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: DOM Assignee: annevk@annevk.nl Reporter: harald@alvestrand.no QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org The current language concerning DOMError and DOMException says: Warning: This entire section will move out of DOM into IDL. DOMException will be defined in terms of JavaScript and made available in both document and worker environments. DOMError will be phased out. ..... Warning: DOMError is defined here but only used in other specifications. DOMError will be phased out in favor of using DOMException exclusively. See Creating your own errors on es-discuss for more details. This language does not, I believe, give clear advice on how to deal with DOMError. A suggested rewording: Warning: In the future, DOMException will be defined as a synonym for some yet-unnamed construct in the Javascript specification. The definition given here may be referenced until such a time as this construct is available. .... Warning: New specifications should not inherit from or use DOMError in their specifications. This definition is only preserved in this document to make a stable reference for specifications that inherit from or use DOMError today. Once all those specifications are updated to not use DOMError, the definition of DOMError will be removed from future versions of this document. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 4 June 2014 09:07:07 UTC