-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Incorrect error reporting when using link preload #10381
Comments
Thanks for the report @valodzka i'll check it out. @wardpeet the favicon is a separate issue - we run headless chrome which will never request a favicon. we've removed favicon from perf budgets #10190 but we should also go a bit further I think ... can you open an issue for this? I'd expect the favicon request to not even be made ... |
@valodzka that's weird! could you add a second js file (and also preload it), but give it some content in the body? just I see it is blocked b/c of CSP. devtools log:
which seems wrong ... it's the same origin. That may be our bug. |
Added. Empy or not it doesn't matter. |
P1.5 because this seems like a legit PSI infra bug that deserves to be looked into. edit by paul: it's possible #7163 is related? |
Describe the bug
Incorrect error reported "Browser errors were logged to the console"
To Reproduce
Run web.dev audit with 'https://condescending-haibt-2d0d42.netlify.com/bug.html' (page uses
link: </empty.js>; rel="preload"; as="script"; crossorigin="anonymous"
header)In the report there are incorrect error "Browser errors were logged to the console":
Expected behavior
There should not be such error
Report: https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https://condescending-haibt-2d0d42.netlify.com/bug.html
The text was updated successfully, but these errors were encountered: