- From: Alex Komoroske <komoroske@google.com>
- Date: Tue, 22 Jan 2013 09:11:02 -0800
- To: Chris Mills <cmills@opera.com>
- Cc: "public-webplatform@w3.org" <public-webplatform@w3.org>
- Message-ID: <CAPwaZpVww5qKKZeuqyWsNK_wXGkmaKHLCBUggzmtm1cFprL_CQ@mail.gmail.com>
On Sat, Jan 19, 2013 at 2:29 AM, Chris Mills <cmills@opera.com> wrote: > Cheers Alex! That was a lot of work yesterday ;-) > > Although I did say I might not be finished until Monday - I got up to > about row 510, but the ones below I didn't get to. I would still like to > look over these, just to record the specs each one is defined in, and add > any other properties that may come to light from looking through the specs. > This shouldn't take me long, but I want to check with you first before > doing anything that changing the spreadsheet again won't muck up the > calculations/processing you've applied to it. How is best to proceed here? > Go ahead and edit the Manual Data page; you won't mess anything up. > > Also, this is likely to not be an exhaustive list of CSS properties. We > are likely missing a lot of SVG-CSS properties. Do we want to add the > missing ones in, or should we defer those to a later SVG task? I suggest > the latter. > I agree that the latter is best. > > Best, > > Chris Mills > Opera Software, dev.opera.com > W3C Fellow, web education and webplatform.org > Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M) > > On 19 Jan 2013, at 02:36, Alex Komoroske <komoroske@google.com> wrote: > > > Hi all, > > > > Thanks to some epic work and encycopledic knowledge of CSS by Chris, we > now have the standardization status for all of the 574 CSS properties in > our exhaustive list of every CSS property known to man. > > > > I've taken a first stab at assigning priorities to them in the main > tracking sheet: > https://docs.google.com/a/chromium.org/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZRzMtWEdyU0Z4OEE#gid=0 > > > > Here's the guidelines I tried to apply: > > • > > • P0 - Must have right this instant: (often because they're > important to developers based on MDN's popularity data) > > • P1 - Necessary to complete milestone > > • P2 - Normal priority. The majority of these should be done for > the milestone to be considered finished. > > • P3 - Not necessary for milestone, should have at some point in > the future > > • P4 - Not a priority ever > > Let me know if you see any articles that you think are too highly > ranked, and any that aren't ranked high enough. > > > > Meanwhile, Mike Sierra is taking a stab at making our representative CSS > article. Once he's done (and we've discussed it) then we'll work on the > guide to writing css property docs. > > > > --Alex > >
Received on Tuesday, 22 January 2013 17:12:02 UTC