Add requestDevice User Prompt BiDi Extension Section to Bluetooth Spec

[outofambit]

Summary

Specify a WebDriver BiDi extension that grants control over user prompts produced by the Web Bluetooth API.

Location of spec prose

Precedent exists in webdriver classic for specifying extensions in the relevant specification of the given technology rather than in the webdriver spec. The BTT Working Group has signaled that this is how it should work for BiDi.

Primary Goal

Allow a web developer to test their application using Web Bluetooth and automate responding to user prompts.

How this is different from Permissions

This extension will automate responding to a user prompt produced by navigator.bluetooth.requestDevice, which allows a user to choose a specific device to connect to. A side effect of requestDevice is granting permission to access a specific device.

The WebDriver BiDi group is already working on a general permissions extension. Automation of the browser powerful feature permissions required by navigator.bluetooth.requestDevice will be handled by that extension.

---

References

• https://webbluetoothcg.github.io/web-bluetooth/
• https://github.com/webbluetoothcg/web-bluetooth/
• Permissions API Extension #613
• Extend roadmap: permissions automation w3c/webdriver-bidi#523
• Meta: WebDriver BiDi extensions w3c/webdriver-bidi#506
• https://w3c.github.io/webdriver-bidi/
• https://w3c.github.io/webdriver-bidi/#command-browsingContext-handleUserPrompt
• https://w3c.github.io/webdriver-bidi/#event-browsingContext-userPromptOpened
• https://www.w3.org/TR/webdriver2/#user-prompts
• https://chromedevtools.github.io/devtools-protocol/tot/DeviceAccess/
• https://www.w3.org/TR/permissions/