- From: Reilly Grant via GitHub <noreply@w3.org>
- Date: Fri, 10 Apr 2026 00:20:44 +0000
- To: public-web-bluetooth-log@w3.org
Yes, the Bluetooth blocklist is intended to extend to the `requestLEScan` method. The iBeacon example is a bad one and this decision is at least partially forced upon implementations by platforms like Android that differentiate between location and non-location usage of Bluetooth (the `neverForLocation` manifest property). An application needs to choose a global value for this and since the web platform has a dedicated Geolocation API it seems better to allow a compliant Web Bluetooth implementation to make this assertion. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/669#issuecomment-4218796405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 April 2026 00:20:45 UTC