CSS animations not completed properly on Chrome 49 Canary and FF nightly

[majido]

Context: There is an ongoing effect to change Event.timeStamp from epoch time to a high-res timestamp. This meas that Event.timeStamp is no longer going to be comparable to Date.now() due to different time origins but rather may be compared to performance.now(). This feature is currently enabled by default in Chrome 49 Canary (all platforms) and Firefox 44 developer edition (on certain platforms).

Issue: In angular, the logic for triggering animation completion for css animations depends on comparing Date.now() (i.e., startTime) with incoming animation event timestamp which is causing issues for certain types of animations (example.

Here is the original report on Firefox bugzilla which has some additional details.

Potential fix: A simple fix is to use Date.now() instead of event.timeStamp here. This is already the fallback option which is in fact being used for Firefox (FF has 0 for timestamp!). It should not have any really impact given that the current Event.timestamp is not much different from Date.now() when event handler is invoked.

[majido]

/cc @matsko @Narretz

[petebacondarwin]

Duplicate of #13494