Skip to main content

Google Chrome enables new Bluetooth permissions settings UI behind flag

Google Chrome now provides users with more control over Web Bluetooth Permissions to let websites reconnect to permitted Web Bluetooth devices. It not only exposes Web Bluetooth permissions to Site Settings and Page Info but also enables users to exercise more control over Web Bluetooth permissions, Techtsp has learned.

Since Web Bluetooth permissions are currently not visible in Chrome’s Settings UI, users have been unable to control permissions for Web Bluetooth devices, something Chrome 85 intends to address.

Chrome 85 allows users to control Bluetooth permissions in settings UI, courtesy of an experimental feature Use the new permissions backend for Web Bluetooth behind chrome://flags. In Site Settings, users can choose if they want a particular website to access a Bluetooth device temporarily or persistently.

1. Bluetooth devices entry in Site Settings page

2. Bluetooth device permission page in Site Settings

Users will be able to revoke site access to devices here or block Web Bluetooth entirely.

3. Bluetooth devices entry in Site Details page

Users will be able to block Web Bluetooth for a given site in this menu.

4. Bluetooth device permissions in Page Info

Users will be able to quickly revoke device permissions for the current site or block Web Bluetooth for the site.

How to enable the Use the new permissions backend for Web Bluetooth flag in Google Chrome

  1. Open Google Chrome
  2. Open chrome://flags
  3. Locate Use the new permissions backend for Web Bluetooth
  4. Set the flag to Enable immediately using the drop-down menu
  5. Relaunch Chrome

Chrome users can revoke Bluetooth access they might have granted to a website or grant a website permissions to temporarily access a Bluetooth device.

Chrome already supports the Web Bluetooth API. But it doesn't help websites maintain a persistent Bluetooth connectivity with supported devices for several reasons:

The Web Bluetooth API has no way to provide users with a list of devices that a website has permission to access. That is why the Web Bluetooth API has to prompt the user every time the Bluetooth-enabled device is loaded. Chrome 85 will make use of the Bluetooth.getDevices() method to receive a list of Bluetooth devices that a website has access to.

Then, the Bluetooth adapter logic in Chrome also removes permitted Web Bluetooth devices that have been inactive for more than 3 minutes. To fix this issue, Chrome is now adding a new method to its existing BluetoothAdapter.

Google’s Web Bluetooth Persistent Permissions will be compatible across Windows, Mac, Linux, ChromeOS, and Android.

Related Articles

Chrome 87 to remove support for non-standard RTP data channels in WebRTC

See Google's fingerprint payment prototype on Desktop in action

Google Chrome users can receive SMS messages on desktop in the near future

Google Chrome set to release Tab Search feature behind experimental flag