The additional boolean `webSocketUrl` capability is used to request a WebDriver BiDi websocket: https://w3c.github.io/webdriver-bidi/#establishing Similar to the `moz:debuggerAddress` capability it needs to be forwarded to Marionette, which then takes care about the creation of the Websocket in Firefox. When `webSocketUrl` is set it should be asserted for `true`. Returned will be a WebSocket URI: https://w3c.github.io/webdriver-bidi/#construct-a-websocket-url James, what actually defines the secure bit of the WebSocket connection? I assume that we should basically use it by default and only fallback if a secure connection cannot be established? I don't see how a client could actually request that.
Bug 1692984 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.
The additional boolean `webSocketUrl` capability is used to request a WebDriver BiDi websocket: https://w3c.github.io/webdriver-bidi/#establishing Similar to the `moz:debuggerAddress` capability it needs to be validated by Marionette, and has make sure to create to return the Websocket URL. When `webSocketUrl` is set it should be asserted for `true`. Returned will be a WebSocket URI: https://w3c.github.io/webdriver-bidi/#construct-a-websocket-url James, what actually defines the secure bit of the WebSocket connection? I assume that we should basically use it by default and only fallback if a secure connection cannot be established? I don't see how a client could actually request that.