-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Exception "unrecognized performance logging option: enableTimeline" when setting options using latest chromedriver #5481
Comments
Given that the official ChromeDriver documentation shows that is valid, can you help me understand what the proper JSON payload should be? Should the |
This area is not very well documented, and I can't find sources I had about the version the timeline change was made... EDIT: another similar bug report stating that timeline is no longer available: https://groups.google.com/forum/#!topic/chromedriver-users/132rOz35-gs |
…river According to chromedriver bug #2034 (https://bugs.chromium.org/p/chromedriver/issues/detail?id=2034), the enableTimeline performance logging preference is no longer accespted by chromedriver.exe. The .NET language bindings will no longer send that preference to the driver executable. Additionally, the peroperty setting the preference has been deprecated, and will generate a compile-time warning. The property will be remvoed in a future release. Fixes issue #5481.
Fixed in commit b1a7d4d. |
OS:
Windows 7
Selenium Version:
3.8.0
Browser:
Chrome
Browser Version:
63.0.3239.132
ChromeDriver version:
2.35.528161
We are initializing ChromeDriver with options as follows:
On every run, the ChromeDriver constructor throws the following exception:
Issue is caused by method:
OpenQA.Selenium.Chrome.ChromeOptions.GeneratePerformanceLoggingPreferencesDictionary()
Which initializes a logging option entry named 'enableTimeline'. This option is not recognized by newer versions of ChromeDriver (2.21 and up AFAIK, could be even earlier), causing the exception to be thrown.
The text was updated successfully, but these errors were encountered: