Description
related to #16117
In all bindings, when we start chromedriver, we should pass the --enable-chrome-logs argument. This allows chromedriver to inherit the i/o streams from the browser process. Without this, we have no way to suppress or redirect browser i/o streams, which results in unwanted logging going to the user's console.
JavaScript bindings already do this, but all other bindings do not.
Note: I am not sure if Edge supports this or a similar flag.
Description
related to #16117
In all bindings, when we start
chromedriver, we should pass the--enable-chrome-logsargument. This allows chromedriver to inherit the i/o streams from the browser process. Without this, we have no way to suppress or redirect browser i/o streams, which results in unwanted logging going to the user's console.JavaScript bindings already do this, but all other bindings do not.
Note: I am not sure if Edge supports this or a similar flag.