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 15813 - TypeError shouldn't be referenced as a DOMException
Summary: TypeError shouldn't be referenced as a DOMException
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-31 17:07 UTC by Odin Hørthe Omdal
Modified: 2012-03-09 20:51 UTC (History)
4 users (show)

See Also:

Attachments

Description Odin Hørthe Omdal 2012-01-31 17:07:47 UTC 
Every place that the spec is referencing TypeError, it's calling it a DOMException. That doesn't exist. It should either be TypeMismatchError, or more believable: a JavaScript TypeError exception.
Comment 1 Eliot Graff 2012-03-09 20:51:59 UTC 
This change was made to the three instances of TypeError. Pushed live this morninig.