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 27284 - Should InvalidAccessError be discouraged?
Summary: Should InvalidAccessError be discouraged?
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 27283
  Show dependency tree / graph
 
Reported: 2014-11-08 19:27 UTC by Domenic Denicola
Modified: 2016-12-08 09:39 UTC (History)
5 users (show)

See Also:

Attachments

Description Domenic Denicola 2014-11-08 19:27:44 UTC 
It seems like uses of it should be either TypeError (for invalid arguments) or NotSupportedError (for unsupported operations).

See also https://www.w3.org/Bugs/Public/show_bug.cgi?id=27283
Comment 1 Jerry Smith 2014-12-02 19:11:01 UTC 
This bug affects Encrypted Media Extensions, which currently specifies using InvalidAccessError in cases where invalid argument values are encountered.

EME bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=27283 recommends changing this to TypeError.  Both Media Source Extensions and Web Crypto follow this convention.
Comment 2 David Dorwin 2015-10-19 23:29:15 UTC 
Moved to https://github.com/w3c/encrypted-media/issues/103.
Comment 3 David Dorwin 2016-09-20 04:24:15 UTC 
Oops, that was an EME bug that was moved. I don't know whether the WebIDL issue has been addressed.
Comment 4 Tobie Langel 2016-12-08 09:39:25 UTC 
Fixed by https://github.com/heycam/webidl/commit/671706d