Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Some browsers support requestAnimationFrame, so why not use it? After all, it’s been supported since Google Chrome 10. Despite that, jQuery does not seem to be using it. I’ve found a bug report about it, but no real explanation was given? I’m sure the jQuery people have their reasons, though.
Why wouldn’t they use this awesome API?
In ticket #9381 you can read why they stopped using
requestionAnimationFrameafter some time.To summarize, problems were that animations didn’t run (browsers try to reduce CPU load) when window didn’t have focus, which is OK if the window is hidden, but not if it is visible, just out of the focus. Furthermore, animation queues piled up and after window regained focus, things went berserk. This would require ugly changes in the code and/or changes how people add things to the animation queue. So it was decided that support is removed until there is some better way to do this.