- From: Jatinder Mann <jmann@microsoft.com>
- Date: Fri, 11 May 2012 17:21:30 +0000
- To: James Robinson <jamesr@google.com>
- CC: Nat Duca <nduca@chromium.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>
> I've made this change in 458:4843fb42912f along with defining that the callback's parameter is gathered > by running the window.performance.now() algorithm before any callbacks are invoked. This means that > one script-observable side effect is that the parameter will always be <= the value that script could observe > by running window.performance.now() in the callback, and it's not something like an expected > presentation time that may be in the future. > > Can you confirm whether this is consistent with what you intend to ship in IE10, Jatinder? My understanding > is that this is consistent with Mozilla and Chrome's expected behavior. Yes, this is consistent with what we plan to ship in IE10. The callback's parameter will not reflect a future presentation time and will be <= performance.now(). Thanks for making the updates to the spec. Jatinder
Received on Friday, 11 May 2012 17:22:40 UTC