Re: Fullscreen API

On some level it doesn't matter where this gets done. But on a technical level, the full screen API has little to do with CSS and almost nothing to do with SVG.

 - Maciej

On Feb 8, 2011, at 10:14 AM, Doug Schepers wrote:

> 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
> 
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG, WebApps, and Web Events WGs
>

Received on Tuesday, 8 February 2011 18:23:48 UTC