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
Describe the bug
Lighthouse shows the error "Browser errors were logged to the console".
The description of the error is "Access to XMLHttpRequest at 'https://clientapi.passle.it/CookieControlPlugin/CookieControl' from origin 'https://environment.johnbosley.dev' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."
The resource at https://clientapi.passle.it/CookieControlPlugin/CookieControl has the header Access-Control-Allow-Origin: *, and the console error reported is not logged when visiting the URL https://environment.johnbosley.dev in the browser.
Access-Control-Allow-Origin: *
This issue doesn't occur when testing using the devtools, but it does occur when using web.dev.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The best practices section shouldn't show any errors.
Screenshots
The text was updated successfully, but these errors were encountered:
Here's a link to the report. https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fenvironment.johnbosley.dev%2F
I think this might be a PSI issue. Moving over to the LH repo as they also manage PSI.
Describe the bug
Lighthouse shows the error "Browser errors were logged to the console".
The description of the error is "Access to XMLHttpRequest at 'https://clientapi.passle.it/CookieControlPlugin/CookieControl' from origin 'https://environment.johnbosley.dev' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."
The resource at https://clientapi.passle.it/CookieControlPlugin/CookieControl has the header
Access-Control-Allow-Origin: *
, and the console error reported is not logged when visiting the URL https://environment.johnbosley.dev in the browser.This issue doesn't occur when testing using the devtools, but it does occur when using web.dev.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The best practices section shouldn't show any errors.
Screenshots
The text was updated successfully, but these errors were encountered: