[Bug 25441] Overconstrained muted state should not link with MediaStreamTrack.readyState

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25441

--- Comment #2 from Kiran <kiran.guduru@samsung.com> ---
(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."

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Received on Friday, 25 April 2014 11:53:55 UTC