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 27749 - "DOMException constructor object" as IDL
Summary: "DOMException constructor object" as IDL
Status: RESOLVED INVALID
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-05 10:53 UTC by Simon Pieters
Modified: 2015-01-05 10:59 UTC (History)
3 users (show)

See Also:

Attachments

Description Simon Pieters 2015-01-05 10:53:25 UTC 
https://heycam.github.io/webidl/#es-DOMException-constructor-object

[[
DOMException constructor object
]]

Why is DOMException specified as prose instead of as IDL (with prose for things not expressable in IDL, if anything)? Having it as IDL has the advantage of being easier to test and maybe also implement.
Comment 1 Anne 2015-01-05 10:58:10 UTC 
Because there's no IDL to express Error objects properly.
Comment 2 Simon Pieters 2015-01-05 10:59:10 UTC 
I forgot that it's not an interface so I guess direct prose makes sense.