Animation slowdowns in Chrome 13

[mootools]

Animation slowdowns in Chrome 13

[oskarkrawczyk]

You can actually notice these slowdowns in the accordion one the left - http://jsfiddle.net

[arian]

Hmm, don't see anything weird in 13.0.782.107 (Developer Build 94237 Linux) Ubuntu 11.04

[oskarkrawczyk]

We're noticing this on Chrome 13.0.782.107 (stable), OS X (10.6)

Pretty crappy if this is an OS specific issue.

[jonnsl]

it is not an OS specific issue, is a webkit issue https://bugs.webkit.org/show_bug.cgi?id=22102 ,the bug tracker says that this bug is related to Macintosh Mac OS X 10.5 but it is also reallys slow on ubuntu and on windows

[oskarkrawczyk]

Not really using box-shadow anywhere in JsFiddle, yet the animation is awfully jumpy.

Actually, this release of Chrome is full of bugs, specifically with css animations/transforms.

I guess this issue can be closed since it's not a MooTools bug... Then again, if they don't fix this until the next release, perhaps it's a good moment to start thinking about a workaround, or the next phase of Fx (I assume that would be this little thing called CSS Animations).

[ibolmo]

Also on Chrome 14.0.835.18 dev Mac OS X 10.7 no issues. Looks like a Chrome 13 issue. Perhaps we should notify people as a known issue, but we'll leave it as wont fix since it'll fix itself in matter of weeks (when Chrome 14 goes stable).

[cpojer]

Please next time think about these kinda things before opening a ticket in the wrong place:

"I can't provide a real test-case for this. But as I see it, in version 12, the animation was smooth from 0% to 100%, but in version 13 […] it simply has these random slowdowns."

I don't see how you could blame a JS library for this by having such a description and no test case at all.

[oskarkrawczyk]

Christoph, instead of being all you towards my person (yes, I'm aware you're not very fond of me), please read my last comment.

I'm not blaming the library, I'm pointing out that there's AN issue - you (core developers) should be aware of those. It doesn't matter if I post it here or on the dev list, as long as it's noticed by you guys.

[ibolmo]

Yeah that wasn't nice @cpojer. Any report is better than no report.

[cpojer]

I understand that and thank you for you report. Given this is obviously a temporary browser bug it is unlikely that we are considering to fix this. Please use the ticket system on github strictly for actual things we can fix and post other stuff on the mailing list.

@ibolmo is there a way to encourage users to only open a ticket if they have reproducible tests? I don't want us to waste time on might-be bugs.

[ibolmo]

I'm willing to spend 2 minutes on a bad ticket another 2 to explain (nicely) how to make a (proper) ticket. So that someone else spends 25 minutes trying to figure out a problem and 5 minutes to write a ticket. :D