Hi Maciej, thanks for the clarification.
I would suggest that if, as in this case, Hixie rejects a feature without convincing the WHATWG community that the data, use cases etc do not support the introduction of a feature, then the WHATWG process is broken. regards SteveF On 30 November 2012 06:18, Maciej Stachowiak <m...@apple.com> wrote: > > On Nov 29, 2012, at 10:00 PM, Steve Faulkner <faulkner.st...@gmail.com> wrote: > >> maciej wrote: >> >>> The WHATWG has pretty clearly rejected the idea of the <main> element >> >> >> can you point to a clear rejection in any of the relevant threads on >> the WHATWG apart from hixies? >> >> I would suggest the WHATWG has general support for adding main, but I >> may not be understanding what is meant by a whatwg rejection in this >> case. > > I mean that by the whatwg process, if Hixie says no clearly and definitively, > that is the decision. I say this not to judge, just to describe what it is. > This does not of course mean that everyone who participates in the WHATWG > agrees. > > The only thing I see as likely to change things in the whatwg is > implementations appearing. > > Regards, > Maciej > -- with regards Steve Faulkner Technical Director - TPG www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
