[whatwg] [html5] r6630 - [giow] (0) Define navigating to video and audio resources Fixing http://www.w3.o [...]
ian at hixie.ch
Thu Oct 6 10:56:23 PDT 2011
On Thu, 6 Oct 2011, Bjartur Thorlacius wrote:
> On Wed, 05 Oct 2011 17:37:22 -0000, Ian Hickson <ian at hixie.ch> wrote:
> > On Wed, 5 Oct 2011, Simon Pieters wrote:
> > >
> > > video and audio should have controls="" and autoplay=""
> > The spec allows browsers to do that (in fact it explicitly calls out
> > autoplay=""), but do we really want to require one or the other? I can see
> > arguments for having only one or the other or both.
> Autoplaying is obviously subject to user preference, but I see no point
> in not providing controls (assuming the output rendering is interactive,
> of course). Theoretically speaking, those controls should of course be
> stylable. That that may well be difficult to implement, however.
The context here is how browsers display videos when you just navigate to
a video file directly. Much as with navigating to images, where the spec
says to use <img> but doesn't require or disallow extra features, such as
the zoom feature most brosers provide, we here just say to use <video>,
and then leave the UI up to the UA.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg