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

The ability to register multiple event listeners is inherited from the rest of the web platform. The reason `startNotifications()` and `stopNotifications()` are critical for Web Bluetooth is that events can bubble up the [Bluetooth tree]( from the `BluetoothRemoteGattCharacteristic` they are fired against (though this is currently unimplemented in Chrome). Starting and stopping notifications implicitly based on whether an event listener was registered would not provide the information necessary to know which characteristic to start notifications on since the event listener could be registered higher up the tree.

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

Received on Monday, 29 October 2018 21:38:14 UTC