[Bug 10419] <video> should allow muted as a content attribute

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10419

--- Comment #9 from Philip Jägenstedt <philipj@opera.com> 2010-10-13 13:39:14 UTC ---
(In reply to comment #8)
> How about we add an audio="" attribute that controls the audio channel of the
> <video>?

And of <audio>, I presume? <audio audio=muted> is a bit weird, but volume and
pitch control is not.

> It would take a space-separated list of tokens, with the following meanings:
> 
> * "off": disable the audio channel entirely, as if the video data had no audio
> track.
> 
> * "muted": if present when the media resource is loaded, set .muted to true,
> overriding user preferences.

Having both "off" and "muted" seems unnecessary, just "muted" would do.

> * a floating point number from 0.0 to 1.0: if present when the media resource
> is loaded, set .volume to the given value, overriding user preferences. (Only
> one such value allowed; ignore all but the first.)

It's slightly easier to use the last one, if you consider what the code that
loops over the list of tokens looks like.

> In the future we could add new values, too, like maybe "do-not-pitch-correct"
> which would disable the pitch correction when changing playbackRate. Also,
> maybe we don't need all the values above in the first version -- in particular,
> we might not need the volume control or "off" initially.
> 
> This gets around the various reflection problems, still allows all the various
> user preference models and "mute" UIs that people have proposed, and isn't a
> pain to type ("audio=muted" is pretty self-explanatory and doesn't feel
> verbose).

It seems mostly OK to me, but are there other cases of multiple related
keywords being space-separated and put in the same attribute?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 13 October 2010 13:39:19 UTC