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 25441 - Overconstrained muted state should not link with MediaStreamTrack.readyState
Summary: Overconstrained muted state should not link with MediaStreamTrack.readyState
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-24 11:39 UTC by Kiran
Modified: 2014-05-08 07:47 UTC (History)
3 users (show)

See Also:


Attachments

Description Kiran 2014-04-24 11:39:35 UTC
In Media Capture and Streams spec, in section 10 Event summary [1] (non-normative) while explaining overConstrained event, it is stated as 

"The affected track(s) will remain un-usable (in the "muted" readyState)",

readyState referring to MediaStreamTrack.readyState. But MediStreamTrack.readystate has no muted attribute, instead this statement can be modified to 

"The affected track(s) will remain un-usable (in the "muted" state)" 

to match with the other parts of the spec (without any link to MediStreamTrack.readystate).

[1] http://www.w3.org/TR/mediacapture-streams/#event-summary
Comment 1 Adam Bergkvist 2014-04-25 11:29:08 UTC
I think we can just say "muted" and have it as a link to where the muted concept is explained in the spec.

I'm not sure we should say "un-usable" in the text. A muted track renders silence or blackness and whether that's usable or not is up to the application.
Comment 2 Kiran 2014-04-25 11:53:53 UTC
(In reply to Adam Bergkvist from comment #1)
> I think we can just say "muted" and have it as a link to where the muted
> concept is explained in the spec.
> 

Of course we can do like that.

The only reason, that I suggest to put muted state is to attain uniformity with the remaining parts of the spec. (In many of the remaining places of the spec state is used along with muted/unmuted). 

> I'm not sure we should say "un-usable" in the text. A muted track renders
> silence or blackness and whether that's usable or not is up to the
> application.

yes we can remove un-usable and make the stentence as below

"The affected track(s) will remain "muted" (link to muted as proposed by Adam) until the application adjusts the constraints to accommodate the source's capabilities."

or

"The affected track(s) will remain in muted state until the application adjusts the constraints to accommodate the source's capabilities."
Comment 4 Stefan Hakansson LK 2014-05-08 07:47:03 UTC
Fixed in http://dev.w3.org/2011/webrtc/editor/archives/20140507/getusermedia.html