W3C home > Mailing lists > Public > public-html-comments@w3.org > July 2010

Re: Fulscreen Tag Proposal

From: Philip Jägenstedt <philipj@opera.com>
Date: Wed, 21 Jul 2010 12:49:33 +0200
To: "Ron Reiter" <ron.reiter@gmail.com>, "Paul Ellis" <paul@ellisfoundation.com>
Cc: "Daniel Hendrycks" <kondo8@hotmail.com>, "public-html-comments@w3.org" <public-html-comments@w3.org>
Message-ID: <op.vf6wcve4atwj1d@philip-pc>
On Wed, 21 Jul 2010 00:20:37 +0200, Paul Ellis <paul@ellisfoundation.com>  
wrote:

> Any solution that requires creating another window and opening a new
> document would create a lot of issues that would not compare favorably  
> with
> any current popular web video plugin (Flash, Silverlight, etc). It would  
> not
> be a very seemless transition. The <video> resource from the parent page  
> may
> have downloaded hundreds of MB of data and then the new window would  
> make a
> new separate request for the same resource. Certainly the browsers could  
> try
> to aggressively cache video content for these situations but even that
> wouldn't work in all cases (any HTTP connection that doesn't allow byte
> range requests, e.g. HTTP 1.0), and it probably would not work very well  
> for
> resource constrained devices such as smartphones and tablets. This type  
> of
> hand-off would have to happen every time the user switched between
> fullscreen and embedded mode as well.

Browsers can and do cache resources that don't support byte ranges. About  
the topic at hand, I think the experience we want is to click a button or  
select "fullscreen" in the context menu, causing an element to go to  
fullscreen, still with the possibility of rendering some content on top of  
it, for custom controls and the like.

-- 
Philip Jägenstedt
Core Developer
Opera Software
Received on Wednesday, 21 July 2010 10:51:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 June 2011 00:14:04 GMT