W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2014

Re: FYI: Navigation Error Logging

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 11 Feb 2014 16:34:13 +0000
Message-ID: <CADnb78gwuvsKsQBr5xL3eq-bn6NuORv4tn4+9+aJoikUDsGj+g@mail.gmail.com>
To: Philippe Le Hegaret <plh@w3.org>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>, public-script-coord <public-script-coord@w3.org>
On Tue, Feb 11, 2014 at 3:56 PM, Philippe Le Hegaret <plh@w3.org> wrote:
> This specification defines an interface to store and retrieve error data
> related to the previous navigations of a document:
>   http://www.w3.org/TR/2014/WD-navigation-error-logging-20140211/
>
> One question that we received recently is about using Promises instead of callbacks:
>  http://lists.w3.org/Archives/Public/public-web-perf/2014Feb/0001.html

Yes, you want promises.

As said during your meeting in China, I'm not sure we can actually
expose more error information than just "network error". There's a
related thread on this here:
http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/thread.html#msg254

As also said during your meeting, I think this should be merged with
resource timing. Tracking resources that resulted in network errors
and resources that succeeded in different lists is annoying. If we're
going to have a list of fetched resources associated with a document
(have you figured out the scope yet?) we should just have one.


-- 
http://annevankesteren.nl/
Received on Tuesday, 11 February 2014 16:34:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:38 UTC