[🐛 Bug]: [dotnet] Remove logging API for non-Chromium browsers

[nvborisenko]

Description

Currently the method to get logs throws exception like it is not supported in Firefox. It will be better just to remove this unsupported method from FirefoxDriver, so users see only supported functionality at compilation time. Seems only Chromium based browsers only support it.

Context:

• [🐛 Bug]: C# Firefox driver get logs throws 'The getLog command returned an unexpected error. HTTP method not allowed' #14744
• [py] Remove logging API for non-Chromium browsers  #15641

Reproducible Code

var driver = new FirefoxDriver();

driver.Manage().Logs.GetLog(LogType.Driver);

[selenium-ci]

@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[nvborisenko]

Most interesting part that currently we have no way to fix it.

class FirefoxDriver : IWebDriver;

interface IWebDriver
{
  IOptions Manage();
}

interface IOptions
{
  ILogs Logs {get;}
}

IOptions opts = driver.Manage();
ILogs logs = opts.Logs; // user even should not be able to write this code for Firefox
logs.GetLog(...);

It will be possible after breaking the hierarchy #14065. If we will rework that to driver.Logs.GetLog(...) then we will be able to specify which functionality is supported per browser.

I feel .NET API is overcomplicated. The same in python looks very simple:

driver.get_log('browser')

Interesting that only python has simple API, all other follow driver.manage.logs.get() pattern. And in my opinion it would be better to driver.logs.get().

CC: @YevgeniyShunevych @RenderMichael

[RenderMichael]

This is currently governed by the marker interface ISupportsLogs.

We can move the Logs functionality into that interface so users will have to do something like this:

((ISupportsLogs)driver).GetLog(LogType.Driver);

This style would be an improvement (marker interfaces are not considered best practice) and is very compatible with an obsoletion process.