- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 22 Mar 2007 01:41:23 +0000 (UTC)
On Thu, 22 Mar 2007, Ian Hickson wrote: > > * The "mute" feature is IMHO better left at the UI level, with the API > only having a single volume attribute. This is because there are > multiple ways to implement muting, and it seems better to not bias the > API towards a particular method. > > (I've seen three major muting interfaces: a mute button that sets a > temporary override which is independent of volume, a mute button that > simply sets the volume to zero, and a -20dB button that you hit two or > three times to get to 0.) > > Having said that, without a mute API, the UA and the author UI can't > stay synchronised with respect to mute state. It was pointed out to me that the above reasoning was weak. I've added 'muted' to the spec. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 21 March 2007 18:41:23 UTC