Re: [web-bluetooth] Clarify the role of requestDevice vs requestLEScan (#255)

requestLEScan() has a prototype that can be experimented with behind flags,
however development is currently paused.
https://www.chromestatus.com/feature/5346724402954240
https://github.com/WebBluetoothCG/web-bluetooth/blob/gh-pages/implementation-status.md#scanning-api
chrome://flags/#enable-experimental-web-platform-features
https://googlechrome.github.io/samples/web-bluetooth/scan.html
https://puckjs-temperature.glitch.me/ source

watchAdvertisements() implementation is underway, and can also be
experimented with now behind flags.
https://www.chromestatus.com/feature/5180688812736512
https://crbug.com/654897
chrome://flags/#enable-experimental-web-platform-features
chrome://flags/#enable-web-bluetooth-new-permissions-backend

On Tue, Jun 9, 2020 at 11:16 PM Peter Strøiman <notifications@github.com>
wrote:

> Thanks for the reply 👍. Is this actively being worked on? As this issue
> is close to 4 years old, I assume an update is not just around the corner.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/WebBluetoothCG/web-bluetooth/issues/255#issuecomment-641749516>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAC6PGY372OWNXHPIMIXHODRV4QMXANCNFSM4CKU53VA>
> .
>


-- 
GitHub Notification of comment by scheib
Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/255#issuecomment-642262957 using your GitHub account

Received on Wednesday, 10 June 2020 21:06:18 UTC