Why does webkit not provide support for native CSS3 attributes in its
parsing engine where those attributes clearly coincide with most other
browsers' attributes -and- the Candidate Recommendations set forth by W3?
Let me put it this way: What is the purpose of every browser having
their own nearly-identically named attributes that take the same
arguments, which are also the same as the attributes set forth in the
Candidate Recommendation?
What makes -webkit-column-gap and -moz-column-gap and column-gap
different from each other aside from the name, and if that's true, why
is there even a name difference?
Is it a waiting game? Or is it possible to take the initiative and
adopt early the attributes recommended? Is there too much risk involved
in early adoption even where there's already nearly complete consensus
among vendors?
--M.Pemrich
Matthew A. Pemrich
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
