Got it - hear you loud and clear. The article wasn't worded correctly. We've corrected the explanation and linked to the APIs directly (which we should have done from the start).
Yeah, we're a tabloid and, yes, we're rude. But at The Reg, we do take accuracy extremely seriously. We want to be right. If you spot anything wrong, [email protected] goes straight to our editors: it's a great way to get things fixed fast. Thanks.
Re:Chrome 56 adds Web Bluetooth API
by GeneralMaximus on Tuesday February 07, 2017 @04:20AM
(#13588184)
Thank you for fixing the error :)
It's a shame many people would make their opinions about Bluetooth API on such poor journalism as The Register offers. Zero credibility!
The API allows a webpage to ask for access to a device in response to a user action only. At this point the user has to give the page permission to access Bluetooth devices. The browser then prompts the user to choose a device from a list of available devices, and the webpage is granted access to whichever device the user picks. That's all. There's no "list every Bluetooth device in the area" API (at least not yet), unless I'm missing something.
More reading: https://medium.com/@jyasskin/the-web-bluetooth-security-mode...
And also: https://medium.com/@urish/is-now-a-good-time-to-start-using-...
And also also: https://developers.google.com/web/updates/2015/07/interact-w...