bluetooth: Check the order of event and promise resolution for readValue

third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/add-multiple-event-listeners.html

Index: third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/add-multiple-event-listeners.html
diff --git a/third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/add-multiple-event-listeners.html b/third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/add-multiple-event-listeners.html
index 6b2d2bc893d059cbc6fa1492005db0dadaadb0b4..44b5c1948b7eb9cd4d24e04cd95553fb4420ba96 100644
--- a/third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/add-multiple-event-listeners.html
+++ b/third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/add-multiple-event-listeners.html
@@ -17,8 +17,7 @@ promise_test(() => {
       return assert_event_fires_after_promise(characteristic,

[scheib, 2017/04/21 06:32:12]

legacy issue, but still:

It's a bit odd that the test method name mentions 'event' before 'promise', but
in the argument list the promise generating function comes before the event
name.

Maybe swap 'event' and 'promise' in the method name, or swap the argument order.

[ortuno, 2017/04/26 05:56:18]

Totally agree. Done.

                                               'startNotifications',
                                               'characteristicvaluechanged',
-                                              3 /* add 3 listeners */,
-                                              false /* ignore_event_promise_order */);
+                                              3 /* add 3 listeners */);
     })
     .then(() => char.stopNotifications())
     .then(() => assert_no_events(char, 'characteristicvaluechanged'));