This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Do not use event.timeStamp anymore #13494
Labels
Milestone
Comments
|
Landed as e020b89 |
cadams500
pushed a commit
to SparkPost/angular.js
that referenced
this issue
Oct 5, 2023
Due to recent changes in Chrome, Firefox and Webkit use of the event.timeStamp value will lead to unpredictable behaviour due to precision changes. Therefore it's best to stick entirely to use `Date.now()` when it comes to confirming the end of transition- ending values. See angular#13494 for more info. Applies to 1.2, 1.3, 1.4 and 1.5. Closes angular#13494 Closes angular#13495
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With the forthcoming releases for Firefox 44 and new versions of Chromium and Webkit, the use of
event.timeStampwill yield a different value compared to what it did before. Therefore for this reason, all versions of ngAnimate will make use ofDate.now()to leverage timing values within animations.Original bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c3
Changes to Chromium:
https://code.google.com/p/chromium/issues/detail?id=160524
The text was updated successfully, but these errors were encountered: