Re: [lots] -webkit prefixed properties and values

> On 10 Dec 2015, at 09:21, Ms2ger <ms2ger@gmail.com> wrote:
> 
> On 12/09/2015 05:15 PM, Dean Jackson wrote:
>> 
>>> On 10 Dec 2015, at 08:19, Tab Atkins Jr. <jackalmage@gmail.com>
>>> wrote:
>>> 
>>> Per the Compat Spec <https://compat.spec.whatwg.org/>, there's a 
>>> decent-sized list of CSS at-rules, values, and properties that
>>> need to be supported with a -webkit- prefix in order to be
>>> web-compatible: 
>>> <https://compat.spec.whatwg.org/#css-compat-section>.
>>> 
>>> Since implementors have to support these in order to
>>> realistically support web content, they should be listed
>>> alongside the features in the relevant specs (rather than
>>> sidelined into an easy-to-miss errata document like they
>>> currently are).
>> 
>> I disagree. The existing implementors (obviously) know about these
>> properties. New implementors are unlikely to start from scratch.
>> And even if they do, the number of new implementors that appear
>> each year can be rounded to about zero.
>> 
> 
> As an implementor that started from scratch, I disagree.

What are you disagreeing with? That there are about zero new
implementations? Or that we should put these properties in the spec?

FWIW, I realise Servo exists. I wasn’t trying to suggest that it shouldn’t
be counted. I should have said that it is extremely unlikely that a 
starting-from-scratch implementation will only consider the canonical
W3C specifications and pretend everything else doesn't exist.

As for the prefixed properties, it’s not clear to me what criteria is
necessary for it to be considered essential enough to document.
e.g. -moz-column-count or -moz-animation.

Dean