Re: The perils of prefixing... or rather trying to unprefix

On 11/6/12 2:00 PM, François REMY wrote:
> Firstly, your property has the unprefixed name from start, so people can
> stop worrying about prefixes in their stylesheet and javascript.

Ah, ok.  That would definitely have helped in this situation, yes.

>         - from the code, the developer has to do ".style.transform='....
> !target(webkit)'" for webkit and the same for firefox (using if?)

That's basically what they're doing now (incorrectly) with property names.

>         - if the syntax happens to be compatible and that the results
> are identical on most entries, the author could even use
> '!target(webkit-1, moz-1)' in one declaration

This would help, though.

>         - final spec is written and browsers want to "unprefix": from
> now, they'll just ignore any "target" declaration (so Opera would ignore
> target(webkit-2)) and use their final algorithm when the value is valid
> under the new syntax.

Indeed.  That would definitely have worked better in this situation.

-Boris

Received on Tuesday, 6 November 2012 22:31:02 UTC