W3C home > Mailing lists > Public > www-style@w3.org > November 2012

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

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 05 Nov 2012 17:53:20 -0800
Message-ID: <50986D90.9090906@mit.edu>
To: www-style list <www-style@w3.org>
Just in case people are interested, when we shipped Gecko 16 with 
support for 'transition' and 'transform' unprefixed (but 
'moz-transition' and 'moz-transform' left in as aliases for the 
unprefixed property) we ran into at least two libraries that break if 
the 'transform' property is supported unprefixed at all.

One is the jquery.transit library.  See 
https://github.com/rstacruz/jquery.transit/issues/86 and 
https://bugzilla.mozilla.org/show_bug.cgi?id=807636 (and things like 
http://stackoverflow.com/questions/13242260/css3-jquery-transitions-not-working-in-firefox 
and whatnot).

The other seems to be a library used by a company called B-Reel.  See 
https://bugzilla.mozilla.org/show_bug.cgi?id=803126 (about 
http://www.google.com/green ) and 
https://bugzilla.mozilla.org/show_bug.cgi?id=790915 (http://razr.com ).

I have tried contacting both, with zero effect so far.

This simply reinforces my reluctance to do any new prefixing in Gecko, 
for what it's worth.  For example, I plan to ship 
getDefaultComputedStyle unprefixed...

Just figured we'd give other UAs a heads-up for when they decide to add 
unprefixed 'transform'.

-Boris
Received on Tuesday, 6 November 2012 01:53:57 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:02 GMT