W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > December 2016

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

From: Emill via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Dec 2016 15:08:22 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issue_comment.created-268266639-1482246501-sysbot+gh@w3.org>
Why was this closed?

Anyway, I could possibly live with the current solution, but then I 
would like to change the order of
> 3. Fire an event named characteristicvaluechanged with its bubbles 
attribute initialized to true at this.
> 4. Resolve promise with this.value.

Now it's impossible to know in the characteristicvaluechanged event if
 the event was sent due to a read response. If the order is reversed, 
one can be sure that after the promise is resolved, the next 
characteristicvaluechanged event will correspond to the read response.

-- 
GitHub Notification of comment by Emill
Please view or discuss this issue at 
https://github.com/WebBluetoothCG/web-bluetooth/issues/274#issuecomment-268266639
 using your GitHub account
Received on Tuesday, 20 December 2016 15:08:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 December 2016 15:08:29 UTC