Closed tsgoldladder closed 4 months ago
I can't reproduce this, but we did fix a cause of the INVALID_URL
error in M123 and looks like you are on M122.
Does this work using a newer version of Chrome (e.g. Chrome beta)?
Ah ok, maybe my Chrome was not updated at the time. I mainly reported on this to help the project, since the error logs asked me to if the error persisted which it did - but it looks like you've solved it already!
On Wed, 6 Mar 2024 at 18:44, Adam Raine @.***> wrote:
I can't reproduce this, but we did fix a cause https://issues.chromium.org/issues/41490473 of the INVALID_URL error in M123 and looks like you are on M122.
Does this work using a newer version of Chrome (e.g. Chrome beta)?
— Reply to this email directly, view it on GitHub https://github.com/GoogleChrome/lighthouse/issues/15855#issuecomment-1981554098, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJFPCEJ5JXBKYNPSHX2UG2DYW5PX7AVCNFSM6AAAAABEIZ734GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRGU2TIMBZHA . You are receiving this because you authored the thread.Message ID: @.***>
FAQ
URL
https://measurable.energy
What happened?
INVALID_URL
What did you expect?
Normal lighthouse report function. Wouldn't begin.
What have you tried?
Mobile and Desktop scans. Mode: Nav Categories: Performance, Accessibility
How were you running Lighthouse?
Chrome DevTools
Lighthouse Version
not sure
Chrome Version
122.0.6261.111
Node Version
No response
OS
Windows 10
Relevant log output