<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">>>On Mon, 8 Mar 2010, balachandar muruganantham wrote:</span><span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">></span></div><div><span class="Apple-style-span" style="font-family: monospace; white-space: pre; "></span><span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">>><i> I have heard from people that there have been a discussion on supporting </i></span></div><div><pre>>><i> the fullscreen mode for HTML5 video element. can anyone share the
</i>>><i> information on the conclusion we arrived at? i searched in the archive
</i>>><i> but i could not come to any conclusion.
</i>
>On March 25th, Ian Hickson then said:</pre><pre>>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.
</pre><div>I hope it's not minded if I weigh in on this topic as I feel strongly about it.</div></div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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."</div><div><br></div><div>Finally, in reference to the CSSOM Ian, I'm not sure this is what you are referring to, but another solution to the fullscreen issue is if the browser default controls could be styled with CSS. This would be a real win-win, as we could have our secure fullscreen button (as implemented in Webkit but not Firefox strangely) and also have a faster path to custom controls.</div><div><br></div><div>While I would guess this would be a CSSOM issue, it seems that it would still be a recommendation by WHATWG.</div><div><br></div><div>
<div>Mike Wilcox</div><div><a href="http://clubajax.org">http://clubajax.org</a></div><div><a href="mailto:mike@mikewilcox.net">mike@mikewilcox.net</a></div><div><br></div><br class="Apple-interchange-newline">
</div>
<br></body></html>