We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When passing chrome flag
--host-resolver-rules='MAP www.example.org:443 127.0.0.1:8443'
to the --chrome-flags flag, lighthouse requests the original https://www.example.org/ as usual, simply ignoring the host-resolving rule.
I guess there is some code like split(' ') used so that flags which contain inner space will be divided and discarded.
I also wonder whether there is a way to bypass this problem.
The text was updated successfully, but these errors were encountered:
Hey there @AltF4Top thanks for the report! Indeed this is a current limitation and is captured by #2753, #2754 is in progress to address this.
Sorry, something went wrong.
No branches or pull requests
When passing chrome flag
to the --chrome-flags flag, lighthouse requests the original https://www.example.org/ as usual, simply ignoring the host-resolving rule.
I guess there is some code like split(' ') used so that flags which contain inner space will be divided and discarded.
I also wonder whether there is a way to bypass this problem.
The text was updated successfully, but these errors were encountered: