For the [WebDriver HTTP specification](https://w3c.github.io/webdriver/) we have an existing but only partial documentation for client developers. This documentation can be found at: https://developer.mozilla.org/en-US/docs/Web/WebDriver. There is also a [MDN issue that discusses plans for further additions](https://github.com/mdn/content/issues/4721). Nevertheless we should make sure to do better for WebDriver BiDi, and as such start early with landing the first pages for client developers. As best this would be a shared effort each stakeholder (browser vendor) could participate in. A clear benefit is that all the content is no longer managed via a Wiki, but directly via Github at: https://github.com/mdn/content/tree/main/files/en-us/web/webdriver. As such writing documentation got way simpler. Important to know for the web content to be added would be the kind of audience we are targeting here. IMO it will primarily be developers of various WebDriver client implementations. As such we should have a clean listing of available commands and events with their used payloads, and parameter types. Also the wording should be easier and easier to understand as the specification itself. The entry point could be: https://github.com/mdn/content/tree/main/files/en-us/web/webdriver_bidi I'll bring-up this topic in tomorrow's monthly WebDriver meeting.
Bug 1720275 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For the [WebDriver HTTP specification](https://w3c.github.io/webdriver/) we have an existing but only partial documentation for client developers. This documentation can be found at: https://developer.mozilla.org/en-US/docs/Web/WebDriver. There is also a [MDN issue that discusses plans for further additions](https://github.com/mdn/content/issues/4721). Nevertheless we should make sure to do better for WebDriver BiDi, and as such start early with landing the first pages for client developers. As best this would be a shared effort each stakeholder (browser vendor) could participate in. A clear benefit is that all the content is no longer managed via a Wiki, but directly via Github at: https://github.com/mdn/content/tree/main/files/en-us/web/webdriver. As such writing documentation got way simpler. Important to know for the web content to be added would be the kind of audience we are targeting here. IMO it will primarily be developers of various WebDriver client implementations. As such we should have a clean listing of available commands and events with their used payloads, and parameter types. Also the wording should be easier and easier to understand as the specification itself. The entry point could be: https://github.com/mdn/content/tree/main/files/en-us/web/webdriver_bidi Further we probably want to feed in [browser compatibility data](https://github.com/mdn/browser-compat-data) to show the compatibility tables listing browser support ([like that one for Array](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array#browser_compatibility)). I'll bring-up this topic in tomorrow's monthly WebDriver meeting.
For the [WebDriver HTTP specification](https://w3c.github.io/webdriver/) we have an existing but only partial documentation for client developers. This documentation can be found at: https://developer.mozilla.org/en-US/docs/Web/WebDriver. There is also a [MDN issue that discusses plans for further additions](https://github.com/mdn/content/issues/4721). Nevertheless we should make sure to do better for WebDriver BiDi, and as such start early with landing the first pages for client developers. As best this would be a shared effort each stakeholder (browser vendor) could participate in. A clear benefit is that all the content is no longer managed via a Wiki, but directly via Github at: https://github.com/mdn/content/tree/main/files/en-us/web/webdriver. As such writing documentation got way simpler. Important to know for the web content to be added would be the kind of audience we are targeting here. IMO it will primarily be developers of various WebDriver client implementations. As such we should have a clean listing of available commands and events with their used payloads, and parameter types. Also the wording should be easier to understand as the specification itself. Automated documentation generation doesn't seem to be feasible at this point. The entry point could be: https://github.com/mdn/content/tree/main/files/en-us/web/webdriver_bidi Further we probably want to feed in [browser compatibility data](https://github.com/mdn/browser-compat-data) to show the compatibility tables listing browser support ([like that one for Array](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array#browser_compatibility)). I'll bring-up this topic in tomorrow's monthly WebDriver meeting.