W3C home > Mailing lists > Public > www-archive@w3.org > February 2012

CSS API Task Force?

From: Doug Schepers <schepers@w3.org>
Date: Tue, 07 Feb 2012 10:42:02 -0500
Message-ID: <4F31464A.7090500@w3.org>
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
CC: Arthur Barstow <art.barstow@nokia.com>, Peter Linss <peter.linss@hp.com>, Bert Bos <bert@w3.org>, Philippe Le H├ęgaret <plh@w3.org>, Charles McCathieNevile <chaals@myopera.com>, www-archive@w3.org, Robin Berjon <robin.berjon@gmail.com>, "chris@w3.org" <chris@w3.org>, team-webapps <team-webapps@w3.org>, Cameron McCormack <cam@mcc.id.au>, Erik Dahlstrom <ed@opera.com>
Hi, folks-

It seems to me that there are several badly-needed and important APIs 
related to CSS that may not have a high priority in the CSS WG itself, 
because of a traditional emphasis on the markup aspects of CSS.

Considering that the WebApps WG is currently being rechartered, and has 
the right set of eyes to drive and review API specs, does it make sense 
to make a joint Task Force between the CSS and WebApps WGs (and maybe 
the SVG WG, which this affects) to handle these deliverables?  The FX TF 
between CSS and SVG WGs seems to be useful and productive, so this is a 
proven model.

Off the top of my head, this would probably include the following specs:
* Fullscreen API
* Selectors API
* Widget Media Feature
* CSS OM
* Font Metric API

If we want to do this, this would mean that all these items should be 
put into scope of the WebApps WG charter.  (Alternately, we could start 
a CSS API WG to focus on these items, also as joint deliverables with 
the CSS WG.)

We would also need to determine a chair for this CSS API TF, to really 
drive these deliverables.

Thoughts?

Regards-
-Doug
Received on Tuesday, 7 February 2012 15:45:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:18:47 GMT