Current CDP implementation allows only a browser-wide "simulated Bluetooth adapter", while specification requires it to be browsing-context specific. Switching to navigable-specific will be a breaking change.

We propose the following: make the "context" parameter of "bluetooth.SimulateAdapterParameters", "bluetooth.SimulatePreconnectedPeripheralParameters" and "bluetooth.SimulateAdvertisementParameters" optional. This would allow for both navigable's specific and global "simulated Bluetooth adapter". For now, until CDP implements navigable-specific "navigable's specific "simulated Bluetooth adapter", the implementation will return an error.

Note that probably "simulated Bluetooth adapter" is user context-specific.