- From: Michael Norton <norto@me.com>
- Date: Thu, 10 Oct 2013 15:13:22 -0400
- To: Ian Hickson <ian@hixie.ch>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Mark Roberts <gbstar@msn.com>
On Oct 10, 2013, at 2:45 PM, Ian Hickson <ian@hixie.ch> wrote: > > Because to get something adopted in a browser, you need to do the > following (not always in this order): > > 1. Have someone design the feature. I have done this. > 2. Have someone write a specification for it. I have begun this. > 3. Have some people write tests for it. > 4. Have one browser implement it. I have via having writ some XUL code had Firefox implement its most important feature. > 5. Have another browser implement it. An associate built a Java browser demo of the same. > 6. Have another browser implement it. > 7. Have another browser implement it. > 8. Have people document it. Not a coder myself, I need funding to hire and coordinate a team to reach the finish line. > > This is in contrast to "everything else", which just needs: > > 1. Someone to implement it. > > >> I would like to see improvements to selectors. The way elements are >> selected on a page is hard work! Why can't a child select a parent in >> hover or any other target? HTML5 is a great advance, but in this case we >> still have to rely on jscript for most things! > > For selectors, I recommend posting to the www-style@w3.org mailing list. > > HTH, > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 10 October 2013 19:13:55 UTC