Re: [Bug 24931] New: the spec defines an interface called “MediaError”, which conflicts with the “MediaError” defined for the MediaElement (video/audio tags)

On 03/04/2014 11:57 PM, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=24931
>
>              Bug ID: 24931
>             Summary: the spec defines an interface called “MediaError”,
>                      which conflicts with the “MediaError” defined for the
>                      MediaElement (video/audio tags)
>             Product: WebRTC Working Group
>             Version: unspecified
>            Hardware: All
>                  OS: All
>              Status: NEW
>            Severity: normal
>            Priority: P2
>           Component: Media Capture and Streams
>            Assignee: public-media-capture@w3.org
>            Reporter: shijuns@microsoft.com
>                  CC: public-media-capture@w3.org
>
> The Media Capture and Streams spec defines an interface called “MediaError”,
> which conflicts with the “MediaError” defined for the MediaElement (video/audio
> tags).
>
> Propose to rename the following through the spec.
>
> 1. from “MediaError” to “MediaStreamTrackError”
> 2. from “MediaErrorEventInit” to “MediaStreamTrackErrorEventInit”
> 3. from “MediaErrorEvent” to “MediaStreamTrackErrorEvent”

Good catch.
I would prefer "MediaStreamError" to reduce the amount of typing.
It is used both on NavigatorUserMediaErrorCallback and in the 
MediaErrorEvent; it is not necessarily bound to tracks only.

It's also been suggested that the error class in the WebRTC spec should 
use this class, since DOMError is now disappearing, and its replacement 
does not seem to be stable yet.

Received on Thursday, 13 March 2014 09:33:18 UTC