782194 - Follow spec for MediaStream and expose the correct attributes and functions

Status: RESOLVED DUPLICATE of bug 910249

(Core :: WebRTC, defect, P3)

Description

[Jason Smith [:jsmith]]

In doing comparison testing on Chrome with our Nightly implementation, I've generally noticed that we are not exposing the correct API attributes or functions at the JS level. Right now, when looking in the web console, we expose something called "currentTime," which represents the time the stream has been running. Chrome I noticed does not expose this, and instead exposes what appears to fall in alignment with what's called out in the API. Examples include:

- audioTracks (Media Stream)
- label (Media Stream)
- onended (Media Stream) 
- readyState (Media Stream)
- videoTracks (Media Stream)
- stop() (LocalMediaStream)

This bug intends to track correcting the exposed API attributes and functions to the LocalMediaStream object returned on a success callback.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This is not only for the LocalMediaStream returned by gUM but for any instance of nsIDOMMediaStream.

Comment 3

[Silvia Pfeiffer]

Actually, being able to distinguish between multiple input video cameras via id and/or label is quite important. We have a multi-camera application that won't work in Firefox yet, unfortunately. And lack of attributes is one of the reasons.

Comment 4

[Thomas Bruun]

We just discovered a bug in our application caused by an assumption that all streams have an id attribute. Any timeframe for when this can be implemented? Is the MediaStream API stable enough to prioritize this?

Comment 5

[Maire Reavy [:mreavy]]

jib - this may be a dup of the bug you have to finish implementing the MediaStream spec (constructors, attributes, etc).  Can you dup this or otherwise update it (and update the priority/rank if so)?  thanks

Comment 6

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

id was added in Bug 1089798.
add/removeTrack is covered by Bug 1103188.
constructor is Bug 1070216.
rest is Bug 910249.