Re: [whatwg] Using time-origin-relative times for the .timeStamp property of animation events is not web-compatible

2015-12-10 Thread Anne van Kesteren 
On Thu, Dec 10, 2015 at 10:00 AM, Boris Zbarsky  wrote:
> It looks like at least the angular-animate assumes that the .timeStamp
> property of animation events produces values that can be compared to
> Date.now() return values.  See
> https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c3 for details.

Added a note to the corresponding issue:

  https://github.com/whatwg/dom/issues/23#issuecomment-163740275


-- 
https://annevankesteren.nl/

[whatwg] Using time-origin-relative times for the .timeStamp property of animation events is not web-compatible

2015-12-10 Thread Boris Zbarsky 
It looks like at least the angular-animate assumes that the .timeStamp 
property of animation events produces values that can be compared to 
Date.now() return values.  See 
https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c3 for details.


-Boris