W3C home > Mailing lists > Public > www-style@w3.org > October 2013

Re: Implementers information

From: Kang-Hao (Kenny) Lu <kanghaol@oupeng.com>
Date: Thu, 17 Oct 2013 07:47:15 +0800
Message-ID: <525F2583.1030305@oupeng.com>
To: Brian Kardell <bkardell@gmail.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
CC: WWW Style <www-style@w3.org>
(2013/10/17 2:55), Brian Kardell wrote:
> It would be real handy information for a community who might want to lobby
> prioritization of certain work...

If that is the use case, then you don't really need internal information
such as "what implementers are actively expending resources toward
implementing". What I would suggest, and what I used to do when I got
started here was

1) Go to the Wikipedia's page "Comparison of layout engines
(Cascading_Style_Sheets)"[1]
2) Go to the bug number linked from the feature I am interested in.
3) Add my self to Cc / Vote on it

It might be useful to fork that page (to a GitHub wiki, say) so that it
contains votes from the community, and I hope the whole page can still
be editable. I have no idea how GitHub wiki's revert feature is and I
hope we don't run into governance issues.

In general, I do agree that folks in this maling list don't have good
data about Web developers' prioritization. However, I have doubts that
having it would change anything in this list. [2] is pretty good from
1-6 for example (I don't think folks care much about Text). A Web
developers' list would probably lack CSS Animations and CSS Transitions
because they think "they'are finished", but really they aren't.

[1]
http://en.wikipedia.org/wiki/Comparison_of_layout_engines_%28Cascading_Style_Sheets%29
[2] http://disruptive-innovations.com/zoo/customers/CSSWG/Priorities.html


Cheers,
Kenny
-- 
Web Specialist, Opera Sphinx Game Force, Oupeng Browser, Beijing
Try Oupeng: http://www.oupeng.com/
Received on Wednesday, 16 October 2013 23:47:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 16 October 2013 23:47:46 UTC