Skip to content
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

Network aborted resources SHOULD be present (not MAY) #242

Closed
yoavweiss opened this issue Jan 18, 2021 · 1 comment
Closed

Network aborted resources SHOULD be present (not MAY) #242

yoavweiss opened this issue Jan 18, 2021 · 1 comment

Comments

@yoavweiss
Copy link
Contributor

In 4.2, we say "Resources for which the fetch was initiated, but was later aborted (e.g. due to a network error) MAY be included as PerformanceResourceTiming objects in the Performance Timeline and MUST contain initialized attribute values for processed substeps of the processing model"

It'd be better to always surface such resource, and test that implementations do. It'd also be good to clarify that e.g. error status code responses are not failed fetches.

@noamr
Copy link
Contributor

noamr commented Sep 29, 2021

Fixed by #290

@noamr noamr closed this as completed Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants