22355 2013-06-13 19:55:41 +0000 Create NavigatoreUserMediaError object with name attribute as appropriate before queuing error callback 2013-06-14 08:58:20 +0000 1 1 1 Unclassified WebRTC Working Group Media Capture and Streams unspecified PC All RESOLVED DUPLICATE 22250 P2 normal --- 1 w3c public-media-capture dom public-media-capture oldest_to_newest 89276 0 w3c 2013-06-13 19:55:41 +0000 In Section 11.1.1 , failure: will not always be PERMISSION_DENIED, it can also be CONSTRAINT_NOT_SATISFIED. The text reason should be the text attribute of the NavigatorUserMediaError object which should be consistently created before invoking the error callback. In addition, eliminate the goto and target and simply queue the error callback as appropriate. Proposed change: (1) Change 2nd bullet in section 11.1.1 from "Optionally, e.g., based on a previously-established user preference, for security reasons, or due to platform limitations, jump to the step labeled failure below." to "Optionally, e.g., based on a previously-established user preference, for security reasons, or due to platform limitations, create a new NavigatorUserMediaError object whose name attribute has the value PERMISSION_DENIED and then queue a task to invoke errorCallback with error as its argument." (2) Change 7.3.1 and 7.3.3 in section 11.1.1 from "and then jump to the step labeled failure below" to "and then queue a task to invoke errorCallback with error as its argument." (3) Remove the entire failure: goto target. Specifically, remove the following: [[ Failure: Let error be a new NavigatorUserMediaError object whose name attribute has the value PERMISSION_DENIED. Queue a task to invoke errorCallback with error as its argument. ]] 89303 1 dom 2013-06-14 08:58:20 +0000 *** This bug has been marked as a duplicate of bug 22250 ***