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

DevTools Error: Failed to construct 'URL': Invalid URL #6979

Closed
Fgruntjes opened this issue Jan 10, 2019 · 5 comments
Closed

DevTools Error: Failed to construct 'URL': Invalid URL #6979

Fgruntjes opened this issue Jan 10, 2019 · 5 comments

Comments

@Fgruntjes
Copy link

Initial URL: https://www.zitmaxx.nl/
Chrome Version: 71.0.3578.98
Error Message: Failed to construct 'URL': Invalid URL
Stack Trace:

TypeError: Failed to construct 'URL': Invalid URL
    at new URLShim (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:4575:1)
    at NetworkRequest.onRequestWillBeSent (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1421:67)
    at NetworkRecorder.onRequestWillBeSent (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1399:151)
    at NetworkRecorder.dispatch (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1409:66)
    at devtoolsLog.forEach.message (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1412:126)
    at Array.forEach (<anonymous>)
    at Function.recordsFromLogs (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1412:93)
    at Function.afterPass (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1115:163)
@exterkamp
Copy link
Member

I can repro this. Some wires are getting crossed somewhere.
image

@brendankenny
Copy link
Member

@exterkamp that looks like that's in the report code (util.js)? But the call stack shows the throw in network-request.js

@exterkamp
Copy link
Member

Yup, I'm still looking. I was thinking of the wrong part of font-size since SEO i18n is still on my mind 😆

Current thought is that a network request has gone bad yea.

@exterkamp
Copy link
Member

Okay I think I found it.

This is a duplicate of #6145 which is fixed by #6157 and should be fixed in post 4.0.0-alpha.0 releases!

In Chrome canary it seems to audit fine. But it should audit fine now as well if you remove the font requests going to https:

I knew it had to do with fonts somehow @brendankenny 😉

@Fgruntjes
Copy link
Author

Guys thnx allot!

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

3 participants