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

[web-bluetooth] Pull Request: Make readValue's .then() and event handlers execute in the same order they're mentioned in the spec.

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Sat, 16 Jan 2016 02:12:11 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <pull_request.opened-56242839-1452910330-sysbot+gh@w3.org>
jyasskin has just submitted a new pull request for 
https://github.com/WebBluetoothCG/web-bluetooth:

== Make readValue's .then() and event handlers execute in the same 
order they're mentioned in the spec. ==
Preview at 
https://rawgit.com/jyasskin/web-bluetooth-1/read-value-ordering/index.html

@g-ortuno I'm being clever here with the adjacent tasks. Could you 
double-check that it looks reasonable to implement? 
`BluetoothDispatcher::OnReadValueSuccess` currently just resolves the 
promise, and doesn't fire any events. To avoid letting another value 
update come in before the event dispatches, we'd either need to run a 
microtask checkpoint (which I could just put in the spec...), queue a 
pair of tasks from `OnReadValueSuccess`, or send two adjacent IPCs to 
get the two tasks queued.

See https://github.com/WebBluetoothCG/web-bluetooth/pull/200
Received on Saturday, 16 January 2016 02:12:14 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 16 January 2016 02:12:14 UTC