[whatwg] <video>

[Shane Fagan]

On Mon, 2010-06-21 at 00:03 +0200, Diego Perini wrote:
> 
> 
> On Sun, Jun 20, 2010 at 11:19 PM, Ashley Sheridan
> <ash at ashleysheridan.co.uk> wrote:
>         
>         On Sun, 2010-06-20 at 22:13 +0100, Shane Fagan wrote: 
>         > On Sun, 2010-06-20 at 16:07 -0500, Mike Wilcox wrote:
>         > > >>On Mon, 8 Mar 2010, balachandar muruganantham wrote:>
>         > > >> I have heard from people that there have been a discussion on
>         > > supporting 
>         > > >> the fullscreen mode for HTML5 video element. can anyone share the 
>         > > >> information on the conclusion we arrived at? i searched in the archive 
>         > > >> but i could not come to any conclusion.
>         > > 
>         > > >On March 25th, Ian Hickson then said:
>         > > >The conclusion was that it is a presentational issue and therefore should 
>         > > >be handled in one of the CSSOM specs. Unfortunately we don't have anyone 
>         > > >who has the bandwidth to edit a spec to specify how to make things go 
>         > > >full-screen. WebKit is experimenting with some APIs in this space, I 
>         > > >believe.
>         > > I hope it's not minded if I weigh in on this topic as I feel strongly
>         > > about it.
>         > > 
>         > > 
>         > > It's very important that the HTML5 spec address developers' needs
>         > > without crippling their abilities due to unfounded or incorrect
>         > > security implementations. This is the problem we've been dealing with
>         > > in regard to the file input uploaders for years, trying to simply
>         > > apply a little CSS style to them.
>         > > 
>         > > 
>         > > Adobe has blocked inappropriate use of fullscreen by tying that
>         > > functionality to the click of a button. It can't be done onload or
>         > > programmatically, it requires a user's interaction. The HTML5 spec can
>         > > provide the same thing for fullscreen video. It's no different than
>         > > the security used for HTML file inputs – you can't open a a File
>         > > Browse Dialog, the user must click a button.
>         > > 
>         > > 
>         > > I sincerely hope developers' needs aren't made secondary in such
>         > > debates. While I appreciate proper browser security, in some cases it
>         > > forces us to just look for workarounds to circumvent the security. The
>         > > lack of fullscreen is a serious issue for us as we deal with clients
>         > > and superiors who ask us to replace the Flash video player with an
>         > > HTML5 video player... only to have us go back to them and say "Here is
>         > > the cool player with custom controls... sorry, you can't do fullscreen
>         > > though, it's not allowed". The obvious response to this is "Flash
>         > > can, why can't HTML5?" and "well, let's just use Flash then."
>         > > 
>         > 
>         > Couldnt we have a property in the video tag that allows full screen?
>         > That would solve what you are saying I think. 
>         > 
>         > 
>         > --fagan
>         > 
>         > 
>         > 
>         
>         
>         Not really. The argument is about abuse of a fullscreen mode.
>         An attribute in the <video> tag would mean it would start in
>         fullscreen mode, which would be the easiest way to abuse it.
>         
>         Thanks,
>         Ash
>         http://www.ashleysheridan.co.uk
>         
>         
>         
> 
> The attribute should only instruct the browser to show the fullscreen
> button in the controls panels and in the context menu and not to
> switch to fullscreen mode immediately.
> 
> This will allow to enforce/maintain a user action as the trigger for
> the fullscreen mode and thus avoid abuse of the feature
> programmatically.
> 
> --
> Diego Perini
> 
> 


That would work +1

--fagan