Log endpoints are not part of official Webdriver API

[johanbrandhorst]

Hi,

I was investigating an issue with not being able to get browser logs from a firefox session and discovered that the /session/<uid>/log API implemented by ChromeDriver (and others?) is not part of the official WebDriver API spec (yet?).

I found https://github.com/mozilla/geckodriver/issues/330 while browsing around, which seems to indicate that the issue is being dealt with in https://github.com/w3c/webdriver/issues/406, but it appears there's still no clear decision on what to do for the official spec.

So, since it's not supported by the official API, should it stay? It doesn't work with my firefox session and may well only be supported by ChromeDriver (and maybe PhantomJS?).

[sclevine]

Hi @johanbrandhorst,

This is because /session/:sessionId/log and /session/:sessionId/log/types were present in Selenium's initial draft for the the spec.

Let's not change the agouti/api package until there's an official decision. We can work around differences in the webdrivers in the agouti package.

[johanbrandhorst]

Sounds good, would we return an error for firefox clients then? It currently spits out a 404 when I try to use the log call.