Awesome work guys. Thanks! On Tuesday, September 23, 2014 6:11:58 PM UTC-7, Valentin Gosu wrote: > As of next week we intend to turn on resource timing. It has been developed > > behind the dom.enable_resource_timing pref. > > > > == Summary == > > > > The Resource Timing API allows web applications to access timing > > information for resources in a document. > > > > == Platform Coverage == > > Resource timing works on all platforms. An issue tracked in bug 1064706 is > > that in e10s the performance.getEntries() will return an empty array. > > > > == Test coverage == > > dom/tests/mochitest/general/test_resource_timing.html > > dom/tests/mochitest/general/test_resource_timing_cross_origin.html > > > > There is also the w3c test, which presents some failures for all UAs > > because of bugs in the test. > > http://w3c-test.org/resource-timing/test_resource_timing.html > > > > == Interop == > > > > Chrome and Opera have prefixed the webkitClearResourceTimings and > > webkitSetResourceTimingBufferSize methods, and the > > onwebkitresourcetimingbufferfull event handler. > > > > == Links == > > http://www.w3.org/TR/resource-timing/ > > https://bugzilla.mozilla.org/show_bug.cgi?id=1002855 > > > > Thanks > > -- > > Valentin
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
