This repository was archived by the owner on Apr 12, 2024. It is now read-only.
fix: Use Date.now() instead of Event.timeStamp to detect animation end#13497
Closed
majido wants to merge 1 commit intoangular:masterfrom
Closed
fix: Use Date.now() instead of Event.timeStamp to detect animation end#13497majido wants to merge 1 commit intoangular:masterfrom
majido wants to merge 1 commit intoangular:masterfrom
Conversation
Chrome and Firefox are planning to change event.timeStamp to be a high resolution time instead of epoch time. This means that the event.timeStamp will not longer be compatible with Date.now()[1, 2] Instead we can use Date.now() at the moment when the event is received by event listener instead. [1] http://crbug.com/538600 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c3
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chrome and Firefox are planning to change event.timeStamp to be a
high resolution time instead of epoch time. This means that the
event.timeStamp will not longer be compatible with Date.now()[1, 2]
Instead we can use Date.now() at the moment when the event is
received by event listener instead.
This addresses #13496
[1] http://crbug.com/538600
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c3