[Bug] Failed to inject content script after retrying

[giorgioskizzo]

🐛 Bug report

Description

Environment

• webhint version: 2.3.1
• Browser version: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36
• URL for which webhint failed:

webhint configuration

webhint’s configuration

Categories:

• [x] Accessibility
• [x] Compatibility
• [x] Performance
• [x] Pitfalls
• [x] PWA
• [x] Security

Your target browsers:

• [x] Recommended settings
• [ ] Custom:

Ignored resources:

• • [x] None
• • [ ] Different origin
• • [ ] Custom:

Debug output

Please include the content of the Error details section if an error message was displayed.

webhint’s Error details

Failed to inject content script after retrying.

[antross]

Thanks for the report @giorgioskizzo! Are you able to share the URL you were trying to analyze with webhint when this error occurred? That would help us reproduce the issue so we can identify what's going on. Thanks!

[giorgioskizzo]

Hi, I'm not testing a url, but a local file. I attached it to this email.

Greetings, Giorgio

On Wed, May 12, 2021 at 6:33 PM Tony Ross @.***> wrote:

Thanks for the report @giorgioskizzo https://github.com/giorgioskizzo! Are you able to share the URL you were trying to analyze with webhint when this error occurred? That would help us reproduce the issue so we can identify what's going on. Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/webhintio/hint/issues/4546#issuecomment-839925096, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACV3YMF6VQUKOGVOELHPR4TTNKUWPANCNFSM44Y56LUQ .

[antross]

@giorgioskizzo unfortunately it looks like the attachment didn't make it from the mail through GitHub.

If this was opened using the file:// it's possible the browser is blocking the extension from accessing the page and you may be able to get it to work if you spin up a local webserver so it can be accessed via localhost. If you're already using localhost then I'm not sure what's up, though we have seen some issues with Content-Security-Policy in the past...

[giorgioskizzo]

Thanks, I'll check it out. You are telling right: I'm accessing the page via file:// method. I'll put the file on a server and give you a feedback.

Best regards Giorgio

On Thu, May 13, 2021 at 11:38 PM Tony Ross @.***> wrote:

@giorgioskizzo https://github.com/giorgioskizzo unfortunately it looks like the attachment didn't make it from the mail through GitHub.

If this was opened using the file:// it's possible the browser is blocking the extension from accessing the page and you may be able to get it to work if you spin up a local webserver so it can be accessed via localhost. If you're already using localhost then I'm not sure what's up, though we have seen some issues with Content-Security-Policy in the past...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/webhintio/hint/issues/4546#issuecomment-840850151, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACV3YMHCSEOJ7CDEXSMI5EDTNRBFFANCNFSM44Y56LUQ .