Re: [web-bluetooth] Don't fire characteristicvaluechanged for Read Responses

Sorry for dropping this issue again. Flic's use of different formats 
over notification vs read counts as a use case in my mind, so that's a
 good argument to expose the difference. Thanks for pointing out that 
we can go down to the xpc layer to get at this bit. It's going to take
 a while for us to implement that on Chromium, so don't hold your 
breath for this to change, but I now think it's the right long-term 

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

Received on Tuesday, 21 February 2017 19:54:14 UTC