This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22153 - DOMError name
Summary: DOMError name
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-23 15:12 UTC by Marcos Caceres
Modified: 2013-06-20 05:30 UTC (History)
4 users (show)

See Also:

Attachments

Description Marcos Caceres 2013-05-23 15:12:16 UTC 
The spec currently says that the name of a DOMError must return the name it was set to. For the sake of platform consistency (between exceptions and errors), it would be helpful if the spec recommended that people use the names from the "error names table" instead of inventing new ones: http://dom.spec.whatwg.org/#error-names-table

I imagine specs that use Futures are going to make extensive use of DOMError, so it would be good to add this now (if the WG agrees with the recommendation).
Comment 1 Anne 2013-06-19 08:40:48 UTC 
It already says: "As with exceptions, the error names table is used." And the specification says: "If an error name is not listed here, please file a bug as indicated at the top of this specification and it will be addressed shortly. Thanks!" What more is needed?
Comment 2 Marcos Caceres 2013-06-19 10:46:53 UTC 
Ok, I see what happened ... When a spec links to DOMError the Note is off screen (see http://dom.spec.whatwg.org/#domerror). Please move the note about the error  names below the IDL box or people won't see it.