W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2010

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Oct 2010 20:14:52 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P6qg0-00060d-Te@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10419

Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |silviapfeiffer1@gmail.com

--- Comment #12 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2010-10-15 20:14:52 UTC ---
(In reply to comment #7)
> Having thought about this, I agree with Hixie that having .muted reflected as a
> content attribute is a bad idea since we want to allow the browser to remember
> the mute setting but we don't want to make that mutate the DOM during parsing.
> However, I think calling the content attribute something else is also a bad
> idea, since muted="" is what most authors would intiutively try to use to mute
> the video with markup. Thus, I think we should follow the precedent set with
> <input value>, .value and .defaultValue, and introduce <video muted> which is
> reflected with .defaultMuted.

Why not use .muted and .currentMutedState - seems more similar to .src and
.currentSrc which is already a pattern for <video> and <audio>

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 15 October 2010 20:14:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:22 GMT