- From: Sebastian Zartner <sebastianzartner@gmail.com>
- Date: Tue, 6 Nov 2012 14:22:40 +0100
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: www-style list <www-style@w3.org>
- Message-ID: <CAERejNYK7Pf7Kk31rydRimhQWeK+F6gcH9=t6pvU3G7wa+12KA@mail.gmail.com>
Just because some JS library developers are not fast enough catching up with unprefixing things in Gecko is not a reason to avoid prefixing. Introducing new / experimental things without prefixing them will cause much more problems in the future in case their sytnax / logic changes. Instead people should be better prepared for what's coming next and support for the prefixed properties should be kept for one or two engine versions before they are completely dropped to give people time to adapt their code. Sebastian On Tue, Nov 6, 2012 at 2:53 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > 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<https://github.com/rstacruz/jquery.transit/issues/86>and > https://bugzilla.mozilla.org/**show_bug.cgi?id=807636<https://bugzilla.mozilla.org/show_bug.cgi?id=807636>(and things like > http://stackoverflow.com/**questions/13242260/css3-** > jquery-transitions-not-**working-in-firefox<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<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<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 13:23:13 UTC