-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
core: remove config navigations #15397
Conversation
"pauseAfterFcpMs": 1000, | ||
"pauseAfterLoadMs": 1000, | ||
"networkQuietThresholdMs": 1000, | ||
"cpuQuietThresholdMs": 1000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are these changing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We apply overrides to these default values when using DT throttling. Previously, this was applied to the values on the fake navigation object constructed during initializeConfig
.
Now that the fake navigation object is removed, we have to apply the overrides to the settings object directly.
/** | ||
* @param {LH.Gatherer.GatherMode} gatherMode | ||
* @param {LH.Config=} config | ||
* @param {LH.Flags=} flags | ||
* @return {Promise<{resolvedConfig: LH.Config.ResolvedConfig, warnings: string[]}>} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no config warnings anymore but there could be in the future I guess. Shouldn't be too hard to add this if we ever want them again.
Config navigations were moved to internal stuff in 10.0: #13881. It was our plan to remove them completely once the legacy path had been removed completely. This PR fulfills the end goal of that plan.
From a user perspective, the only difference should be that we perform 1
about:blank
jump at the start instead of 2. The rest of this is just removing technical debt.Having just one
about:blank
jump makes it easy to fix #15487 as well.