W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2011

Fullscreen API

From: Doug Schepers <schepers@w3.org>
Date: Tue, 08 Feb 2011 13:14:13 -0500
Message-ID: <4D5187F5.30904@w3.org>
To: "public-fx@w3.org" <public-fx@w3.org>
Hi, folks-

(BCC public-webapps, public-html.  Apologies for the cross-post)

Various people in various groups (as well as the community at large) 
have been emphasizing the need for fullscreen functionality.  In the SVG 
WG, we had discussed the ability to make the root element fullscreen 
(this was a request a few years ago), but I like the idea of making 
individual elements (including grouping elements) fullscreen instead. 
The Mozilla FullScreen API [1] looks like a good start on this, and 
WebKit has picked up on this as well.

It's been suggested to bring this to the WebApps WG, but there is no 
clear scope for this in the WebApps WG charter, and I'd be concerned 
about rechartering.  the HTML WG was also suggested, but I as I 
understand it, they are trying to limit any new features for HTML5.

Since a fullscreen mode is presentational, it arguably belongs in the 
CSS WG, but there isn't much work there done in APIs (other than CSS OM).

So, my suggestion is that we work on it in the FX TF; we can add it 
explicitly to the SVG (and perhaps CSS) WG charters, which are up for 
review again soon.

Since this is a public list, the WebApps and HTML WG participants could 
review and comment on it there.  To some degree, it doesn't matter where 
it is done, as long as the right stakeholders are involved, and both the 
SVG and CSS WGs have participation by all the major browser vendors, 
among others.

Thoughts?  Is the FX TF willing to take this on?

[1] https://wiki.mozilla.org/Gecko:FullScreenAPI

-Doug Schepers
W3C Team Contact, SVG, WebApps, and Web Events WGs
Received on Tuesday, 8 February 2011 18:16:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:37 UTC