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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance log for Chrome doesn't work in 4.0.0-alpha.3 #7300
Comments
I met the same error, also Chrome 75, any solution? |
As mentioned in the Chromedriver 75.0.3770.8 changelog - http://chromedriver.chromium.org/downloads - the preference name was changed to |
yeah, looks like a way to get log:
According to https://stackoverflow.com/questions/53049026/selenium-chrome-performance-logs-not-working |
Fixed by commit 6674a23 |
馃悰 Bug Report
With Chrome 75/Chromedriver 75 and NodeJS Selenium 4.0.0-alpha.3 getting the Chrome performance log fails. I think it was introduced in 8edc13b together with the Chromedriver switch to have w3c compliant as default.
This works with Selenium 3.6.0
To Reproduce
Run the following code + use Chromedriver 75 in the same dir and have Chrome 75 installed.
Expected behavior
The code should not return any error.
It generates an error: InvalidArgumentError: invalid argument: perfLoggingPrefs specified, but performance logging was not enabled. However the log is enabled.
Checking the Chromedriver log we can see that the loggingPrefs is filtered out in the "always match part" (since it's only w3c compliant fields).
Is this a Chromedriver error or Selenium or both? It works in 3.6.0 :)
Environment
OS: OSX
Browser: Chrome
Browser version: 75
Browser Driver version: Chromedriver 75.0.3770.90
Language Bindings version: NodeJs 4.0.0-alpha.3
The text was updated successfully, but these errors were encountered: