Re: Public releases prefixes off-by-default (was RE: Unprefixing CSS properties)

I know something like this has been mentioned before, but couldn't such a
group opt a new prefix and thereby avoid most of the politics?  For
example, there is currently wide agreement on implementations of
:-prefix-any.  Being a selector it has a double whammy effect in that it
requires whole rule repeat.  Now, it may not be exact parity with what gets
formalized for :matches but that does not negate the usefulness of finding
out things like how close that parity is between them.  Why not something
that allows the old process to work though (hopefully quicker), provide
unity through wide implementation concensus, etc by adding a more
grassroots prefix that follows something like a 3 major implentations rule
independent of w3c.... Example :-unity-any or if it is part of the process,
name the prefix something indicative like :-early or :-alpha.

-brian
On Nov 18, 2011 1:53 AM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:

> On 11/18/11 9:48 PM, Boris Zbarsky wrote:
>
>> On 11/18/11 6:04 PM, Brad Kemper wrote:
>>
>>> I think that would be fine in the early stages. I hope it doesn't
>>> happen for very popular properties and values that languish for years
>>>
>>
>> If popular properties are languishing for years, then with all due
>> respect this group is not doing the work it's chartered to do. And then
>> the right solution is probably to route around the damage, reach some
>> sort of inter-UA agreement (a la what happened with HTML when it
>> languished for years) on the properties, unprefix, and move on with life.
>>
>
> To be clear, this is the "right" solution if working within the working
> group is just not being feasible.
>
> Obviously, I hope CSS will never come to this....
>
> -Boris
>
>