RE: FPWD of Navigation Error Logging

There certainly was a goal, at least of mine, that this would catch any errors related to any time a UA tried to make a request, whether that was a user initiated navigation, image fetch failure, XHR, etc… Just getting the top level navigation errors will be huge improvement, though it certainly doesn’t cover all cases.

If I recall, the primary reason we limited it was due to cross origin security concerns.

Aaron




From: Arvind Jain [mailto:arvind@google.com]
Sent: Friday, January 31, 2014 9:56 AM
To: Chase Douglas
Cc: public-web-perf
Subject: Re: FPWD of Navigation Error Logging

We have tied this specification to navigations. There is a separate specification to track errors of subresources and that would cover AJAX - but we haven't worked much on it recently.

Arvind

On Fri, Jan 31, 2014 at 9:27 AM, Chase Douglas <chase@newrelic.com<mailto:chase@newrelic.com>> wrote:
No objections here, just a question :). This seems to be scoped to navigation, but wouldn't this mechanism also work for XHR?

Thanks!

-- Chase

On Thu, Jan 30, 2014 at 8:38 PM, Arvind Jain <arvind@google.com<mailto:arvind@google.com>> wrote:
Hello,
We intend to publish the first public working draft of the Navigation Error Logging specification
(https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html)
next week on Feb 6th.
Please let us know if you have any objections by Tuesday, Feb 4th.

Thanks,
Arvind