New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation Error Logging #24
Comments
It is still active, and they'd appreciate a review. |
Reviewed! Via email to their list. http://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0014.html Maybe we should add a link to that to this repo... |
Discussed in NYC; @domenic to re-review. Will probably close after that. |
New draft is much simpler and uses a HTTP header instead of a JS API. Looks pretty good to me: https://cdn.rawgit.com/w3c/navigation-error-logging/new/index.html However I'll note that in the past @slightlyoff has agitated for an API for CSP and this seems to be moving in the opposite direction, so maybe he has opinions? |
Discussed in SF; @slightlyoff concerned about persistence aspect and privacy considerations. We agree that this seems like a "powerful" feature. We'd also like to see an API. @slightlyoff to write up a review. |
@mnot @slightlyoff for context, discussion on why JS API was removed: https://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0023.html |
I think the logic there makes sense. Has any thought been given to if/when SWs interact with reports? |
@slightlyoff good question, we have not. Opened a bug: w3c/network-error-logging#54 (comment) |
Discussed on call 5-aug. Might not be anything to comment on any more. @slightlyoff thinks we can close the issue. |
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html
Needs promises
The text was updated successfully, but these errors were encountered: