Re: [web-bluetooth] Observing characteristic notifications start and stop

Do you know what use cases are there for the Bluetooth tree? The same doesn't exist for the WebSockets api (ie having a globally accessible way to get at all existing connection instances).

It also brings the original concern back a bit. How can I know if some other script will be starting and stopping notifications on a characteristic I'm interacting with? I suppose DOM Events can have arbitrary scripts stopPropagation, etc. but I think of web bluetooth as more of a communications api where I want more control of messages and responses.

GitHub Notification of comment by rajsite
Please view or discuss this issue at using your GitHub account

Received on Monday, 29 October 2018 22:21:27 UTC