We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As stated in https://html.spec.whatwg.org/multipage/imagebitmap-and-animations.html#animation-frames:
To run the animation frame callbacks for a target object target with a timestamp now: [...] Invoke callback, passing now as the only argument, [...]
I understand that now is the current timestamp at time of execution of the callback and confirmed this in Chrome and Firefox.
now
The text was updated successfully, but these errors were encountered:
capricorn86#554@patch: Use current timestamp in requestAnimationFrame…
71c89f6
… callback.
Merge pull request #555 from c-wygoda/task/554-requestAnimationFrame-…
1ec0490
…callback-timestamp #554@patch: Use current timestamp in requestAnimationFrame callback.
Thanks for contributing @c-wygoda! 🙂
There is a fix available now.
You can read more about the release here: https://github.com/capricorn86/happy-dom/releases/tag/v7.0.2
Sorry, something went wrong.
No branches or pull requests
As stated in https://html.spec.whatwg.org/multipage/imagebitmap-and-animations.html#animation-frames:
I understand that
now
is the current timestamp at time of execution of the callback and confirmed this in Chrome and Firefox.The text was updated successfully, but these errors were encountered: