"Provided URL did not match initial navigation URL"

[adamraine]

I've seen this error message pop up on any URL. It's not fatal so it's not breaking anyone, but it's definitely incorrect and could cause confusion.

cc @benschwarz

[adamraine]

This seems to be caused by #15055. Previously we would enable the network monitor after the about:blank jumps but now it gets enabled before. I think we have two options at this point:

• Update the navigation runner so the network monitor is disabled for the about blank jumps
• Remove this error message

[robsonharry]

Just found this as it was causing me some confusion so definitely an issue!

[samkingtwentytwo]

I've just build a batch lighthouse app for work and noticed this!

Is there any way around it until the navigation runner is updated? I merged your recent PR into my project but assuming you've only reduced the number of about:blank jumps and not updated when the network monitor starts?

Only issue for me is I think it mutates the performance scores. Do you think it would because of some sort of redirect? or?

Cheers Google Dev Sir!

[adamraine]

Only issue for me is I think it mutates the performance scores. Do you think it would because of some sort of redirect? or?

I doubt #15397 would change your performance scores. It could just be normal variance or something like that. If/when #15397 lands and you notice a large and consistent difference in perf scores you can file a separate bug.

[samkingtwentytwo]

Hey Adam.

I fixed it by specifying custom throttling parameters like stated in the thread here:

GoogleChrome/lighthouse-ci#430

Thanks!