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: Wed, 16 Jan 2013 10:57:32 -0800
Message-ID: <CAPwaZpXCY1qUWEHTnb-zWGxWGLD0+QCmZafACU=0DTFtbS42vA@mail.gmail.com>
To: Chris Mills <cmills@opera.com>, Janet Swisher <jswisher@mozilla.com>
Cc: Jonathan Garbee <jonathan@garbee.me>, "public-webplatform@w3.org" <public-webplatform@w3.org>
I'm making a fair bit of progress on filling in which spec each one comes
from.

I also asked Janet if she's be comfortable sharing the most popular CSS
Property articles on MDN since that can help us prioritize. I'm resharing
her response here with her permission:

Here is the top ones for the last month (from the more popular to the
less one):
1. background-image
2. background-size
3. box-shadow
4. font-size
5. background-position
6. transform
7. box-sizing
8. display
9. text-overflow
10. background
11. font-family
12. pointer-events
13. border-radius
14. color
15. position
16. text-rendering
17. background-color
18. line-height
19. filter (but more likely the old -ms-filter rather than the new
filter one)
20. text-align
21. cursor
22. list-style-type
23. font-weight
24. overflow
25. -moz/-webkit-appearance



On Tue, Jan 15, 2013 at 10:30 AM, Chris Mills <cmills@opera.com> wrote:

> On 15 Jan 2013, at 18:16, Alex Komoroske <komoroske@google.com> wrote:
>
> > Okay, another check point. I've spent the last few hours wrangling with
> spreadsheet formula syntax.
> >
> > For various reasons, the first sheet in the spreadsheet is fully
> automatically generated based on formulas. The second sheet ("Manual Data")
> is where we can manually apply extra data to specific css-properties
> (modulo prefix), like if it's a shorthand property or if it's on standards
> track.
> >
> > Chris, one area where you could help immediately is for me to fill in
> the Standards-Specific column in the "Manual Data" sheet [1]. Ideally that
> column would list the standardization status of every property, which will
> help for prioritization (and may help inform us when we actually focus on
> editing every article). For example, I imagine the legal values would be
> something like:
> >        <the monolithic CSS specs before 2.1>
> >        CSS2.1
> >        The remaining values are for the status of each individual
> sub-module
> >        R
> >        CR
> >        WD
> >        ED
> >        Proprietary (for anything where no standards discussion has
> started)
> > Does that sound like something you can help with in the next day or so?
> >
>
> Definitely. I will start work on this tomorrow.
>
> >
> >
> > [1]
> https://docs.google.com/a/chromium.org/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZRzMtWEdyU0Z4OEE#gid=13
> >
>
>
Received on Wednesday, 16 January 2013 18:58:19 UTC

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