- From: Chris Lilley <chris@w3.org>
- Date: Wed, 9 Feb 2011 13:00:41 +0100
- To: www-style@w3.org
Forwarding since Anne thinks the best place for a Fullscreen API to be developed would be CSS WG. What does the rest of the WG think? Personally, although it has a presentational aspect (adds a pseudo class, alters the rendering tree in a similar way to absolutely positioned elements) its mostly JavaScript API and does not seem a particularly good fit to CSS WG. The only API stuff here is CSS OM, and there is not a lot of discussion on that, either. This is a forwarded message From: Anne van Kesteren <annevk@opera.com> To: "Doug Schepers" <schepers@w3.org>, "Cameron McCormack" <cam@mcc.id.au> Date: Wednesday, February 9, 2011, 8:50:35 AM Subject: Fullscreen API ===8<==============Original message text=============== On Wed, 09 Feb 2011 01:32:42 +0100, Cameron McCormack <cam@mcc.id.au> wrote: > I originally had it on my todo list, and handed it off to Anne when he > showed interest. It seemed like he could get to it before me. That seems unlikely now though. :/ I will not pick it up before end of June that is. It does make most sense in the CSS WG to me, given the CSSOM, and the introduction of new pseudo-classes. -- Anne van Kesteren http://annevankesteren.nl/ ===8<===========End of original message text=========== -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Wednesday, 9 February 2011 12:00:43 UTC