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 25440 - MediaStreamTrack.readyState has no muted attribute
Summary: MediaStreamTrack.readyState has no muted attribute
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Dominique Hazael-Massieux
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-24 11:28 UTC by Kiran
Modified: 2014-12-15 10:39 UTC (History)
3 users (show)

See Also:

Attachments

Description Kiran 2014-04-24 11:28:42 UTC 
In WebRTC spec [1] in section 9.2.2 Events on MediaStream,
the ready state attribute has been initialized to muted.

But MediaStreamTrack readyState [2] does not contain "muted" state. It contains only new, live and ended states.

enum MediaStreamTrackState {
    "new",
    "live",
    "ended"
};

Since "muted" state is also considered as "live" state [3], perhaps it may be initialized to "live" instead of muted.

or

It should be initialized with "live" if the connection is established (which is the source for a remote stream) otherwise with "live".

[1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#events-on-mediastream
[2] http://www.w3.org/TR/mediacapture-streams/#idl-def-MediaStreamTrackState
[3] https://www.w3.org/Bugs/Public/show_bug.cgi?id=22259
Comment 1 Adam Bergkvist 2014-04-25 10:54:32 UTC 
(In reply to Kiran from comment #0)
> In WebRTC spec [1] in section 9.2.2 Events on MediaStream,
> the ready state attribute has been initialized to muted.
> 
> But MediaStreamTrack readyState [2] does not contain "muted" state. It
> contains only new, live and ended states.

Thanks for spotting this. It's old stuff that hasn't been updated after "muted" was removed as a state. 

> 
> Since "muted" state is also considered as "live" state [3], perhaps it may
> be initialized to "live" instead of muted.
> 
> or
> 
> It should be initialized with "live" if the connection is established (which
> is the source for a remote stream) otherwise with "live".

Do you mean "new" in the latter case?
Comment 2 Kiran 2014-04-25 11:10:39 UTC 
(In reply to Adam Bergkvist from comment #1)
> (In reply to Kiran from comment #0)
> > In WebRTC spec [1] in section 9.2.2 Events on MediaStream,
> > the ready state attribute has been initialized to muted.
> > 
> > But MediaStreamTrack readyState [2] does not contain "muted" state. It
> > contains only new, live and ended states.
> 
> Thanks for spotting this. It's old stuff that hasn't been updated after
> "muted" was removed as a state. 
> 
> > 
> > Since "muted" state is also considered as "live" state [3], perhaps it may
> > be initialized to "live" instead of muted.
> > 
> > or
> > 
> > It should be initialized with "live" if the connection is established (which
> > is the source for a remote stream) otherwise with "live".
> 
> Do you mean "new" in the latter case?

Yes it is "new", Sorry for the typo.
Comment 3 Adam Bergkvist 2014-05-26 14:58:00 UTC 
Perhaps we should revisit this bug when we have the Dookickey (RTPSender/RTPCRecevier) stuff in place. The RTPCRecevier sort of becomes the new source of a track that is received via a PeerConnection.
Comment 4 Harald Alvestrand 2014-10-30 00:20:54 UTC 
The current (Oct 27) state values are "live" and "ended".

So the occurences of "muted" need to be removed.
Comment 5 Harald Alvestrand 2014-10-31 16:42:58 UTC 
Change needed is to move "readyState" to LIVE and "muted" attribute to TRUE.

Dom to make PR.
Comment 6 Dominique Hazael-Massieux 2014-10-31 16:49:59 UTC 
Proposed fix https://github.com/w3c/webrtc-pc/pull/17
Comment 7 Dominique Hazael-Massieux 2014-12-15 10:39:25 UTC 
WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues

Please subscribe to the issues you want to keep watching.