-
Notifications
You must be signed in to change notification settings - Fork 37
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
RT should tell about the failed request and http status code. #22
Comments
Duplicate of #12 - please see that thread. |
@igrigorik Can you elaborate on how this issue is a duplicate of #12? As far as I could understand, #12 does specify what resources should be a part of the resource timing entires but I could not see sufficient markers by which a developer can distinguish between resources that succeeded and those that failed. If that is the case, this issue seems to be a bit different from what is discussed in #12. @nicjansma's comment "There should probably also be a new field on the PerformanceResourceTiming interface to indicate that it is a failure (and possibly, some classification on why)." is more relevant to this but I do not see any follow ups on that. |
@vaibhavtripathi see #12 (comment). There is still a discussion to be had about additional status codes.. and we should open a new issue for that. (and if we're willing to go down this path) |
@igrigorik Thanks a lot. I had missed that particular comment for some reason. |
Is there a reason why failed requests are not being listed in the entries?
ForEach resource, it could iterate as:
The text was updated successfully, but these errors were encountered: