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 21626 - TypeError is referenced, but not defined
Summary: TypeError is referenced, but not defined
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-08 14:49 UTC by Harald Alvestrand
Modified: 2013-04-08 15:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Harald Alvestrand 2013-04-08 14:49:09 UTC 
In the DOMException specification, I find:

  const unsigned short TYPE_MISMATCH_ERR = 17; // historical; use TypeError instead

But TypeError does not seem to be defined in the spec. Is there a problem here?

This is under this section:

 https://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#exception-domexception
Comment 1 Anne 2013-04-08 15:05:37 UTC 
TypeError is a native JavaScript exception. I'll make it read

"historical; use JavaScript's TypeError instead"

after I'm done with some other edits.
Comment 3 Anne 2013-04-08 15:39:51 UTC 
Next commit will add you to the acknowledgments. Keep forgetting that :-(