On 24/09/14 14:27, Valentin Gosu wrote:
> On 24 September 2014 12:08, James Graham wrote:
>
>> On 24/09/14 02:11, Valentin Gosu wrote:
>>
>>> == Test coverage ==
>>> dom/tests/mochitest/general/test_resource_timing.html
>>> dom/tests/mochitest/general/test_resource_timing_cross_origin.html
>>>
>>
On 24 September 2014 12:08, James Graham wrote:
> On 24/09/14 02:11, Valentin Gosu wrote:
>
> > == 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 s
On 24/09/14 02:11, Valentin Gosu wrote:
> == 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
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 app
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 pla
5 matches
Mail list logo