Re: CSS Properties Milestone: Enumerating CSS Properties

On Mon, Jan 14, 2013 at 8:57 AM, Jonathan Garbee <jonathan@garbee.me> wrote:

> Also with this it would be great to have a property page to point to as a
> great example for the content.
>

100% agreed--so much so that it's already in the plan. :-)

>
> So, is there currently a property page that is a shining example of how
> things should be done for the rest, or is it something that needs to be
> made?
>

Not yet. When I complete the survey (later today) I'm going to try to
identify one. Before the announcement we used font-size as our
demonstration one, because it was both straightforward but also a slight
bit complex.

>
> -Garbee
>
>
> On Mon, Jan 14, 2013 at 7:18 AM, Chris Mills <cmills@opera.com> wrote:
>
>> I would be happy to help with this. How can I pitch in? Would it help for
>> me to go through the specs (CSS 2, CSS3 modules?) and check them to see if
>> there is anything missing from your list?
>>
>> Or if they have been checked sufficiently, I could help you add
>> priorities/fill in the exists column.
>>
>> Just let me know what's best - I obviously don't want to end up
>> duplicating work.
>>
>> 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 12 Jan 2013, at 01:30, Alex Komoroske <komoroske@google.com> wrote:
>>
>> > 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:
>> >       • 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)
>> >       • 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
>> >       • Go through other listings I can find (e.g. MDN) to make sure my
>> list is a superset of properties
>> >       • Take note of which ones appear to be non-standards track (e.g.
>> -webkit-appearance)
>> >       • 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)
>> >       • 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
>> >
>>
>>
>>
>