🐛 Bug Report
A clear and concise description of what the bug is.
When using latest Selenium 4 image with RemoteWebdriver and chrome standalone 4.0.0-alpha-5-20200326 docker image all kind of logs are empty. Problem does not exists in case of using local chrome browser (ver 80.0.3987.149 ).
To Reproduce
- Run standalone chrome docker image from docker hub with selenium 4
- Run tests against image using RemoteWebdriver
- Get logs
AvailableLogTypes count returns 0
Detailed steps to reproduce the behavior:
Expected behavior
There should be 5 types of logs, and at least 2 of them shouldn't be empty (Browser and Driver) - like in case of running this against regular Chrome browser.
Test script or set of commands reproducing this issue
public class RemoteWebriverTests : IDisposable
{
private readonly IWebDriver _driver;
public RemoteWebriverTests()
{
var chromeOptions = new ChromeOptions();
_driver = new RemoteWebDriver(new Uri("http://localhost:4444/"), chromeOptions);
}
[Fact]
public void GetLogsFromChrome()
{
_driver.Navigate().GoToUrl("http://www.youtube.com");
Thread.Sleep(5000);
Assert.True(_driver.Manage().Logs.AvailableLogTypes.Count > 0);
}
public void Dispose()
{
_driver.Quit();
}
}
Environment
OS: Windows 10
Browser: Chrome
Browser version: 80.0.3987.149
Docker image version: 4.0.0-alpha-5-20200326
Browser Driver version: 80.0.3987.10600
Language Bindings version: .net core 3.1
Selenium Grid version : 4.0.0-alpha-5
🐛 Bug Report
A clear and concise description of what the bug is.
When using latest Selenium 4 image with RemoteWebdriver and chrome standalone 4.0.0-alpha-5-20200326 docker image all kind of logs are empty. Problem does not exists in case of using local chrome browser (ver 80.0.3987.149 ).
To Reproduce
AvailableLogTypes count returns 0
Detailed steps to reproduce the behavior:
Expected behavior
There should be 5 types of logs, and at least 2 of them shouldn't be empty (Browser and Driver) - like in case of running this against regular Chrome browser.
Test script or set of commands reproducing this issue
Environment
OS: Windows 10
Browser: Chrome
Browser version: 80.0.3987.149
Docker image version: 4.0.0-alpha-5-20200326
Browser Driver version: 80.0.3987.10600
Language Bindings version: .net core 3.1
Selenium Grid version : 4.0.0-alpha-5