Note that there are some explanatory texts on larger screens.

plurals
  1. POcss3 poor animation performance (Chrome only)
    primarykey
    data
    text
    <p>I'm working on a site using css3 animations, it works perfectly in Safari and Firefox, but for some reason performance in Chrome is awful. (around 15 fps)</p> <p><a href="http://triple-tested.com/animations/" rel="nofollow">http://triple-tested.com/animations/</a></p> <p>The animations are quite simple, basically a few large circles layered up. I've also added a few png sprite animations using javascript.</p> <p>I know about hardware acceleration but I don't think that is the problem, it seems to be some quirk that is unique to Chrome. The css animations perform 'OK' alone but once I add the sprites performance drops considerably. </p> <pre><code> $.fn.spriteme = function(options) { var settings = $.extend({ framerate: 30 }, options); return this.each(function(){ var $el = $(this), curframe = 0, width = settings.width, fr = 1000/settings.framerate; (function animloop(){ if(curframe == settings.frames) { curframe = 0; } $el.css('background-position', (curframe*width)*-1 + 'px center'); curframe++; setTimeout( animloop, fr ); })(); }); }; </code></pre> <p>This is the code I've wrote to animate my sprites, but as I said it performs perfect in Safari and Firefox so I don't think it's the problem. Chrome seems to have an issue with animating using css alongside sprites.</p> <p>I've tried everything I can find online but if anyone has any suggestions please let me know.</p> <p>I'm using the latest stable chrome on mac btw (17.0.963.93)</p> <p>You can see the css (using less) here btw <a href="http://triple-tested.com/animations/css/style.less" rel="nofollow">http://triple-tested.com/animations/css/style.less</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload