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 22216 - NavigatorUserMediaError should inherit from DOMError
Summary: NavigatorUserMediaError should inherit from DOMError
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-30 15:04 UTC by Dominique Hazael-Massieux
Modified: 2013-08-27 08:55 UTC (History)
3 users (show)

See Also:


Attachments

Description Dominique Hazael-Massieux 2013-05-30 15:04:16 UTC
Based on my understanding of our discussions on error handling, NavigatorUserMediaError should inherit from DOMError to use the behavior of the object as defined in the DOM spec.

Also, I think the names of errors in DOMError are camel-cased rather than uppercase (uppercase names were used to define constants matching integer values assigned to the deprecated code attribute); so the errors for getUserMedia should be "PermissionDenied" and "ConstraintNotSatisfied".

I don't think these values should be defined as an enum — that doesn't bring us anything, and it doesn't align with what the DOM spec does (nor other APIs AFAICT); instead, the prose should simply say which errors get raised in what conditions.
Comment 1 Paul Neave 2013-08-21 13:50:33 UTC
It looks as though DOMError is being dropped in favor of DOMException: http://dom.spec.whatwg.org/#domerror

How does this impact NavigatorUserMediaError?
Comment 2 Harald Alvestrand 2013-08-27 08:55:22 UTC
Resolved in 20130824 version of MediaCapture.