Please make sure to do a security review so that this doesn't expose any sensitive information accidentally. In particular, is there any way to use this API to use :visited hacks along with timing information to see if a user has visited a particular URL?
/ Jonas On Mon, Apr 27, 2015 at 2:27 AM, Hiroyuki Ikezoe <hiike...@mozilla-japan.org> wrote: > Summary: Provides an interface for receiving frame performance timing > including composites happening on a separate thread/process. This can > be used to calculate measures of smoothness that incorporate the > effect of async pan and zoom and off-main thread animation. > > Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1158032 > > Link to standard: https://w3c.github.io/frame-timing/ > > Platform coverage: all platforms > > Estimated or target release: Firefox 43 although we might hold off > shipping depending on the state of the spec at that time (there has > been discussion of replacing the buffer-based interface with an > observer interface). > > Preference behind which this will be implemented: dom.enable_frame_timing > > DevTools bug: No specific bug yet but the DevTools team is aware of > our intention to implement and indicated they could use this API. > > Other browser support: Blink: in development, soon to reach Canary.[1] > > [1] https://code.google.com/p/chromium/issues/detail?id=120796#c53 > > Thanks, > > hiro > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
