W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] Volume and Mute feedback on <video>

From: Eric Carlson <eric.carlson@apple.com>
Date: Fri, 20 Aug 2010 14:02:15 -0700
Message-ID: <476C5349-BE28-452B-BCF4-5D6D44DBEC97@apple.com>

On Aug 20, 2010, at 1:49 PM, Roger H?gensen wrote:

> On 2010-08-20 21:57, Ian Hickson wrote:
>> On Mon, 31 May 2010, Silvia Pfeiffer wrote:
>>> I just came across a curious situation in the spec: IIUC, it seems the
>>> @volume and @muted attributes are only IDL attributes and not content
>>> attributes. This means that an author who is creating an audio-visual
>>> Webpage has to use JavaScript to turn down (or up) the loudness of their
>>> media elements or mute them rather than just being able to specify this
>>> through content attributes.
>> What is the use case for overriding the user's defaults in this way?
>> I guess I could see a use case for muting (e.g. video ads often start
>> off muted), but declaring the default volume seems very strange.
> I must say that content has no business messing wit the mute.
> So whatever the user has chosen as default audio or video behavior should be respected at all times, no exceptions.
> I.e. If the browser is "muted" then playback should be muted as well.
  'muted' and 'volume' attributes, if added, would only change the audio output of a media element. A media element's audio is attenuated by the browser volume/mute (if it exists), which is in turn attenuated by the system settings. 

Received on Friday, 20 August 2010 14:02:15 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:26 UTC