WebDriver: Missing endpoints

[AtkinsSJ]

WebDriver is the API for remote-controlling a Browser process, as used by WebPlatformTests. It has a lot of different endpoints, so to make it clear which ones are missing, here's a handy list!

To add an endpoint you'll need to modify the code in two places: The WebDriver end at Userland/Services/WebDriver, and the Browser end at Userland/Services/WebContent/WebDriver*. Comment here or refer to this issue in your PR to get your endpoints checked off the list. :^)

You can find the same table in the spec at https://w3c.github.io/webdriver/#endpoints

• [x] POST /session New Session
• [x] DELETE /session/{session id} Delete Session
• [x] GET /status Status
• [x] GET /session/{session id}/timeouts Get Timeouts
• [x] POST /session/{session id}/timeouts Set Timeouts
• [x] POST /session/{session id}/url Navigate To
• [x] GET /session/{session id}/url Get Current URL
• [x] POST /session/{session id}/back Back
• [x] POST /session/{session id}/forward Forward
• [x] POST /session/{session id}/refresh Refresh
• [x] GET /session/{session id}/title Get Title
• [x] GET /session/{session id}/window Get Window Handle
• [x] DELETE /session/{session id}/window Close Window
• [x] POST /session/{session id}/window Switch To Window
• [x] GET /session/{session id}/window/handles Get Window Handles
• [x] POST /session/{session id}/window/new New Window
• [ ] POST /session/{session id}/frame Switch To Frame
• [ ] POST /session/{session id}/frame/parent Switch To Parent Frame
• [x] GET /session/{session id}/window/rect Get Window Rect
• [x] POST /session/{session id}/window/rect Set Window Rect
• [x] POST /session/{session id}/window/maximize Maximize Window
• [x] POST /session/{session id}/window/minimize Minimize Window
• [x] POST /session/{session id}/window/fullscreen Fullscreen Window
• [x] GET /session/{session id}/element/active Get Active Element
• [x] GET /session/{session id}/element/{element id}/shadow Get Element Shadow Root
• [x] POST /session/{session id}/element Find Element
• [x] POST /session/{session id}/elements Find Elements
• [x] POST /session/{session id}/element/{element id}/element Find Element From Element
• [x] POST /session/{session id}/element/{element id}/elements Find Elements From Element
• [x] POST /session/{session id}/shadow/{shadow id}/element Find Element From Shadow Root
• [x] POST /session/{session id}/shadow/{shadow id}/elements Find Elements From Shadow Root
• [x] GET /session/{session id}/element/{element id}/selected Is Element Selected
• [x] GET /session/{session id}/element/{element id}/attribute/{name} Get Element Attribute
• [x] GET /session/{session id}/element/{element id}/property/{name} Get Element Property
• [x] GET /session/{session id}/element/{element id}/css/{property name} Get Element CSS Value
• [x] GET /session/{session id}/element/{element id}/text Get Element Text
• [x] GET /session/{session id}/element/{element id}/name Get Element Tag Name
• [x] GET /session/{session id}/element/{element id}/rect Get Element Rect
• [x] GET /session/{session id}/element/{element id}/enabled Is Element Enabled
• [x] GET /session/{session id}/element/{element id}/computedrole Get Computed Role
• [x] GET /session/{session id}/element/{element id}/computedlabel Get Computed Label
• [ ] POST /session/{session id}/element/{element id}/click Element Click
• [ ] POST /session/{session id}/element/{element id}/clear Element Clear
• [ ] POST /session/{session id}/element/{element id}/value Element Send Keys
• [x] GET /session/{session id}/source Get Page Source
• [x] POST /session/{session id}/execute/sync Execute Script
• [x] POST /session/{session id}/execute/async Execute Async Script
• [x] GET /session/{session id}/cookie Get All Cookies
• [x] GET /session/{session id}/cookie/{name} Get Named Cookie
• [x] POST /session/{session id}/cookie Add Cookie
• [x] DELETE /session/{session id}/cookie/{name} Delete Cookie
• [x] DELETE /session/{session id}/cookie Delete All Cookies
• [ ] POST /session/{session id}/actions Perform Actions
• [ ] DELETE /session/{session id}/actions Release Actions
• [x] POST /session/{session id}/alert/dismiss Dismiss Alert
• [x] POST /session/{session id}/alert/accept Accept Alert
• [x] GET /session/{session id}/alert/text Get Alert Text
• [x] POST /session/{session id}/alert/text Send Alert Text
• [x] GET /session/{session id}/screenshot Take Screenshot
• [x] GET /session/{session id}/element/{element id}/screenshot Take Element Screenshot
• [x] POST /session/{session id}/print Print Page

[crisdosaygo]

Hey! This will probably seem a really dumb off-hopic noob question jumping onto a tracking issue, so I'm sorry but I was wondering if you folks plan to support WebDriver Bi-directional that utilizes WebSocket?

I thought it was a really useful protocol, and I had a lot of success using an prototype/prehistory implementation of it (Chrome Remote Debugging Protocol / Chrome DevTools Protocol) to create a virtualized remote isolated Browser (BrowserBox).

[AtkinsSJ]

Hey! This will probably seem a really dumb off-hopic noob question jumping onto a tracking issue, so I'm sorry but I was wondering if you folks plan to support WebDriver Bi-directional that utilizes WebSocket?

I thought it was a really useful protocol, and I had a lot of success using an prototype/prehistory implementation of it (Chrome Remote Debugging Protocol / Chrome DevTools Protocol) to create a virtualized remote isolated Browser (BrowserBox).

Hi! I don't know about anyone else but I hadn't heard of the BiDi extension before. We don't really do plans, but that does seem interesting.

The main (only?) reason we're attempting to get WebDriver working is to be able to run the WPT test suite. So that's the focus here for now. But that does look like it would be convenient for building the browser devtools on top of, so we'll see.

[crisdosaygo]

Hey @AtkinsSJ Cool! Yes, it is useful for DevTools. In fact, as you probably already know, the Chrome DevTools is basically a front-end web app interface with functionality to instrument the browser built entirely using these protocol commands (I think ~~ I'm no expert!). The use of the protocol without WebSocket (using HTTP requests) may introduce some weird lag for some things you want to do.

Thanks for your reply, @AtkinsSJ and cool to hear you don't do plans! Very fun! :)

[juliandescottes]

Hi! Just a quick fly-by comment re: webdriver bidi and devtools. As we're implementing WebDriver BiDi in Firefox, we built a small devtools-like frontend at https://github.com/firefox-devtools/bidi-webconsole-prototype

At the moment we only added a "webconsole" and a "netmonitor" (which is really just a list of request), but you could easily do more. We don't really have debugging APIs on the roadmap for the spec yet (https://github.com/w3c/webdriver-bidi/issues/), but maybe in the future we could imagine having a cross browser devtools based on webdriver bidi.

[crisdosaygo]

That's awesome! That is so cool, @juliandescottes. Really happy to see some external devtools that uses the protocol! 😃