W3C home > Mailing lists > Public > public-webplatform@w3.org > January 2013

Re: CSS Properties Milestone: Enumerating CSS Properties

From: Alex Komoroske <komoroske@google.com>
Date: Fri, 11 Jan 2013 17:30:42 -0800
Message-ID: <CAPwaZpXmJc9TxP-uXBQ-UrHsp9qSjOvwx+Ue1U+ZQF0+wo8bOw@mail.gmail.com>
To: "public-webplatform@w3.org" <public-webplatform@w3.org>
Update: I've made a fair bit of progress in the sheet, automatically
concatenating all property names from the WebKit Inspector, WPD, and all of
the prefixed properties from
http://peter.sh/experiments/vendor-prefixed-css-property-overview/ , then
taking only the unique ones (modulo prefix) and keeping track of which ones
came prefixed.

I'll add priorities on Monday (and update the Exists? column with if the
page already exists in WPD).


On Fri, Jan 11, 2013 at 2:20 PM, Alex Komoroske <komoroske@google.com>wrote:

> Hi all,
>
> The first step in the project plan [1] is to enumerate all CSS properties
> so that we can decide which ones are targeted in the milestone and then
> track progress on them.
>
> In the near future we'll want to use Garbee's Bug Genie install, but in
> order to not block I've temporarily started tracking them in a Google
> Spreadsheet [2]. The spreadsheet is world editable, so you don't even need
> a Google Account to edit it (although it is nice for revision history
> reasons if you use one).
>
> My goal is to have this list be an exhaustive enumeration of all CSS
> properties (modulo prefixes) that are accepted by mainstream browsers. It's
> taking longer than I expected!
>
> My work plan is this:
>
>    1. Copy and paste the list of CSS properties from within Chrome's Dev
>    Tools (with any prefixes removed), which is a complete list of all CSS
>    properties that WebKit currently understands (minus the 'shorthand'
>    properties)
>    2. Go through the list of CSS properties on WPD currently [3] to make
>    sure that list isn't missing any, and to keep track of which pages already
>    have a URL on WPD
>    3. Go through other listings I can find (e.g. MDN) to make sure my
>    list is a superset of properties
>    4. Take note of which ones appear to be non-standards track (e.g.
>    -webkit-appearance)
>    5. Go through the list to come up with a preliminary priority
>    breakdown (P0 = Critical, P1 = Important to have, P2 = Good to have, P3 =
>    Not required, P4 = Can wait)
>    6. Circulate for comment with this list.
>
> This is turning out to be quite a bit of work. :-) Let me know if you're
> interested in pitching in on this step.
>
>
> --Alex
>
> [1] http://docs.webplatform.org/wiki/WPD:Tasks/CSS_Property_Milestone
> [2]
> https://docs.google.com/a/chromium.org/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZRzMtWEdyU0Z4OEE#gid=0
> [3] http://docs.webplatform.org/wiki/css/properties
>
Received on Saturday, 12 January 2013 01:31:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:37 UTC