25440 2014-04-24 11:28:42 +0000 MediaStreamTrack.readyState has no muted attribute 2014-12-15 10:39:25 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified All All RESOLVED LATER P2 normal --- 1 kiran.guduru dom adam.bergkvist harald public-webrtc oldest_to_newest 104330 0 kiran.guduru 2014-04-24 11:28:42 +0000 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 104425 1 adam.bergkvist 2014-04-25 10:54:32 +0000 (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? 104430 2 kiran.guduru 2014-04-25 11:10:39 +0000 (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. 106799 3 adam.bergkvist 2014-05-26 14:58:00 +0000 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. 114225 4 harald 2014-10-30 00:20:54 +0000 The current (Oct 27) state values are "live" and "ended". So the occurences of "muted" need to be removed. 114351 5 harald 2014-10-31 16:42:58 +0000 Change needed is to move "readyState" to LIVE and "muted" attribute to TRUE. Dom to make PR. 114354 6 dom 2014-10-31 16:49:59 +0000 Proposed fix https://github.com/w3c/webrtc-pc/pull/17 116310 7 dom 2014-12-15 10:39:25 +0000 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.