W3C home > Mailing lists > Public > public-web-perf@w3.org > December 2017

Re: Resource Timing details for 4xx and 5xx resources

From: Ilya Grigorik <igrigorik@google.com>
Date: Fri, 8 Dec 2017 14:48:54 -0800
Message-ID: <CADXXVKqnKP3ns9+yKTf4akv2qkCVnR2yTPC4OzqqjcHe5ARS4g@mail.gmail.com>
To: Karthik Krishnamurthy <karthik3186@gmail.com>
Cc: public-web-perf <public-web-perf@w3.org>
Hi Karthik.

Relevant discussions:
- https://github.com/w3c/web-platform-tests/pull/4266#issuecomment-263992912
-
https://github.com/w3c/resource-timing/commit/64d7eed8384c563a5a60a90acbfee77f51753b34

The decision is/was that L1 and L2 both specify that the UA *may* surface
such entries. In L3 I'm hoping we can make that a MUST.

ig

On Mon, Nov 27, 2017 at 11:48 AM, Karthik Krishnamurthy <
karthik3186@gmail.com> wrote:

> Hello,
>
> Currently, the way RT data is applied for 4xx and 5xx resources differ
> significantly across browsers. On Firefox and IE (and possibly Edge), RT
> data is fully available for 4xx and 5xx resources (assuming TAO applies).
> However on Chrome, RT data is completely unavailable for 4xx and 5xx
> resources. Two places where this is talked about are:
>
> 1. https://bugs.chromium.org/p/chromium/issues/detail?id=460879#c19
> 2. https://github.com/w3c/resource-timing/issues/12
>
> In both places, it seems like there is an acknowledgement that 4xx and 5xx
> resources behave the same as any other resource and so RT data should be
> available.
>
> The question I have is whether clarification of 4xx and 5xx resources is
> part of the L3 milestones? If so, that might address Chrome's long standing
> issue of not providing RT data for such resources.
>
> Thanks,
> Karthik.
>
Received on Friday, 8 December 2017 22:49:58 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 December 2017 22:49:59 UTC