Prevent flicker on webkit-transition of webkit-transform

Question

Possible Duplicate:
iphone webkit css animations cause flicker

For some reason, right before my animation of the webkit-transform property occurs, there is a slight flicker. Here is what I am doing:

CSS:

#element {
    -webkit-transition: -webkit-transform 500ms;
}

JavaScript:

$("#element").css("-webkit-transform", "translateX(" + value + "px)");

Right before the transition takes place, there is a flicker. Any idea why this is, and how I could fix the problem?

Thanks!

Update: this only occurs in Safari. It does not happen in Chrome, although the animation does work.

Solution 1

The solution is mentioned here: iPhone WebKit CSS animations cause flicker.

For your element, you need to set

-webkit-backface-visibility: hidden;

Solution 2

The rule:

-webkit-backface-visibility: hidden;

will not work for sprites or image backgrounds.

body {-webkit-transform:translate3d(0,0,0);}

screws up backgrounds that are tiled.

I prefer to make a class called no-flick and do this:

.no-flick{-webkit-transform:translate3d(0,0,0);}

Solution 3

Add this css property to the element being flickered:

-webkit-transform-style: preserve-3d;

(And a big thanks to Nathan Hoad: http://nathanhoad.net/how-to-stop-css-animation-flicker-in-webkit)

Solution 4

For a more detailed explanation, check out this post:

http://www.viget.com/inspire/webkit-transform-kill-the-flash/

I would definitely avoid applying it to the entire body. The key is to make sure whatever specific element you plan on transforming in the future starts out rendered in 3d so the browsers doesn't have to switch in and out of rendering modes. Adding

-webkit-transform: translateZ(0) 

(or either of the options already mentioned) to the animated element will accomplish this.

Solution 5

I had to use:

-webkit-perspective: 1000;
-webkit-backface-visibility: hidden;    

on the element, or I would still get a flickr the first time a transition occurred after page load

View more solutions

Comments

[rpitting]

I noticed the very problem in iOS 4.2 beta 2.

[vsync]

happens to me on FF version 17.0 now... with scaled objects that are scaled beyond the size of the window

[Maxime Lafarie]

Behavior always in Chrome in some cases...

[ppcano]

You are right, the backface-visibility fix does not work on image backgrounds. Thanks.

[mlunoe]

My transitions was affecting other elements on the site and I ended up by having to add the rule to all elements on the site.

[Primus202]

Worked for me as well. I had a hidden menu that was pushing the content down with a CSS animation when it was shown. Applying the above rule to my main content div that followed the hidden menu fixed my issue without drastically affecting performance. NB: When I applied it to my global HTML rule it made the CSS animation quite a bit worse, beware!

[pyronaur]

Note, when using translate3d(0,0,0) anywhere Chrome now breaks any background-position: cover that you may or may not have.

[Nguyen Hieu]

Using a wildcard selector for this property actually caused additional flickering from other elements. My working solution was to selectively apply the property to elements that were being translated.

[chovy]

had to add it to parent container too.

[lol]

I think my issue (albeit an intermittent one) was fixed by the universal selector

[mimimimichael]

Use -webkit-backface-visibility: hidden; wisely! I just tried to use it on a scrollable list with images and it caused serious framerate drops.

[aphax]

I would caution against using -webkit-backface-visibility: hidden; as it can cause rendering glitches and make transformed elements appear extremely blurry. I have had some success with using this, but often times it doesn't actually work anyway or I have to go through a lengthy trial and error process to find which elements I have to apply it on. Applying it on all (*) elements has always given me rendering issues with Chrome and I have little hope those will get fixed any time soon.

[Primus202]

PLEASE do not use a wildcard to apply the property to your entire site. Use it sparingly on the troublesome elements. It can drastically reduce performance.

[Dillon]

This is also the way to go with SVGs.

[Fran_gg7]

I am trying but it is not working for me. Here is a code snippet: codeply.com/go/g7Zp98paz5

[bob]

This worked after putting an actual value in: transform: translateZ(0.1px)

[Aust]

None of the answers here worked for me. Not only was I transitioning but I was also changing the overflow property. This answer about -webkit-overflow-scrolling was the solution to my problem.

[KazaJhodo]

I ran into a similar issue... its not exactly the same, however I could see it being relevant in some cases. I had a card flip with a background svg on the backface that was backface-visibility: hidden. On webkit, the background would show until the flip finished, then disappear. My transform was : translateY(180deg). To fix the disappearance in webkit I had to apply, transform: translateZ(-1px) translateY(180deg);, this resolved the disappearance issue. A z-index issue, but of the 3d space, not dom layering. Tricky.

[itsclarke]

this is great - it didn't solve the problem, but it did force my code to be more strict and made tracking down the actual issue easy to find.