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 14991 - Remove DOMError
Summary: Remove DOMError
Status: RESOLVED INVALID
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: 2011-11-29 08:30 UTC by Olli Pettay
Modified: 2011-11-29 09:20 UTC (History)
3 users (show)

See Also:

Attachments

Description Olli Pettay 2011-11-29 08:30:27 UTC 
DOMError in DOM4 seems to be useless. One could just use a string value.

Currently one needs to do filereader.error.name to check the error, 
filereader.error would be simpler.
Comment 1 Jonas Sicking (Not reading bugmail) 2011-11-29 09:05:14 UTC 
The idea is to have a place to stick details about the error in the future. So FileReader.error.bytes could return the set of bytes which wasn't possible to decode using the selected text decoder. Or IDBRequest.error.index could return the name of the specific index whose 'unique' constraint was violated.

These would of course be properties on subclasses of DOMError, and not added to DOMError directly.
Comment 2 Olli Pettay 2011-11-29 09:20:39 UTC 
Ok, that makes sense.