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

CSP issues caused by Lighthouse #13630

Closed
jwpgroup opened this issue Dec 21, 2021 · 1 comment · Fixed by #13636
Closed

CSP issues caused by Lighthouse #13630

jwpgroup opened this issue Dec 21, 2021 · 1 comment · Fixed by #13636
Assignees

Comments

@jwpgroup
Copy link

Hi There

This would seem to be a similar issue to 12525 and 11862, although, in the later case, it has nothing to do with tap targets.

Run this page... https://www.jwp.co.uk/testimonials.html at web.dev and it reports as follows...

Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type Content security policy

In Chrome Dev Tools it says...
"No issues detected so far"

As per the other cases, it's pulling down the score 'Best Practices' score.

Seems like a bug to me. Thoughts?

@jwpgroup jwpgroup changed the title Dec 21, 2021
@devnook devnook transferred this issue from GoogleChrome/web.dev Feb 7, 2022
@adamraine
Copy link
Member

adamraine commented Feb 7, 2022

Yeah this looks like a bug. Something Lighthouse is doing is being blocked by the CSP. This is related to #11862.

I am getting this in DevTools as well.

@adamraine adamraine assigned adamraine and unassigned connorjclark Feb 7, 2022
@adamraine adamraine changed the title Web.Dev reports issues logged in Issues tab, but no issues are shown CSP issues caused by Lighthouse Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants