On Thu, 7 May 2009, Bruce Lawson wrote:
I think the spec should explicity require UAs to provide a mehanism to
mute audio and to pause video, even if the controls attribute is not
set.
We can't require this. Imagine a user agent that is a jumbotron in Times
Square, controlled by just a
On Sat, May 9, 2009, at 2:16 PM, Tab Atkins Jr. wrote:
The issue is that not all browsers have significant configs (I'm
thinking of mobile browsers here), and I don't believe their inability
to provide such a choice to the user should make them nonconforming.
If a UA is incapable of audio
On Tue, May 12, 2009 at 2:07 PM, Erik Vorhes e...@textivism.com wrote:
On Sat, May 9, 2009, at 2:16 PM, Tab Atkins Jr. wrote:
The issue is that not all browsers have significant configs (I'm
thinking of mobile browsers here), and I don't believe their inability
to provide such a choice to the
On Fri, 08 May 2009 02:10:20 +0100, Tab Atkins Jr. jackalm...@gmail.com
wrote:
On Thu, May 7, 2009 at 10:17 AM, Bruce Lawson bru...@opera.com wrote:
Should autoplay be removed as an attribute of audio and video, precisely
to remove such annoyance from people who rely on aural browsing?
On Sat, May 9, 2009 at 2:45 AM, Bruce Lawson bru...@opera.com wrote:
On Fri, 08 May 2009 02:10:20 +0100, Tab Atkins Jr. jackalm...@gmail.com
wrote:
I don't see why this should be a browser requirement. UAs are
*allowed* to provide such a facility to their users, so if your UA
doesn't,
Bruce Lawson wrote:
This may already be in the spec, but I couldn't find it.
I think the spec should explicity require UAs to provide a mehanism to
mute audio and to pause video, even if the controls attribute is not set.
This would not make sense in some situations e.g. for a UA designed to
