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

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 >

Re: [whatwg] Signature Link Relation for Cryptographic Resource Verification

On Wed, Dec 9, 2015 at 10:05 AM, Sean B. Palmer wrote: > I expect that I will be continuing this discussion largely with the > WebAppSpec team, as their work is so obviously related to the contents > of the Internet-Draft. Thank you, that does indeed seem like the right

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

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