W3C home > Mailing lists > Public > public-web-bluetooth-log@w3.org > February 2019

[web-bluetooth] there's no onadvertisementreceived event handler attribute (#426)

From: L. David Baron via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Feb 2019 08:17:52 +0000
To: public-web-bluetooth-log@w3.org
Message-ID: <issues.opened-406221032-1549268271-sysbot+gh@w3.org>
dbaron has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth:

== there's no onadvertisementreceived event handler attribute ==
While this specification *mostly* follows the advice in [ยง3.3. Always add event handler attributes](https://w3ctag.github.io/design-principles/#always-add-event-handlers), I just found one case where it doesn't.  (I offer no promises it's the only case, though.)  The specification has an `advertisementreceived` event, but the target of this event doesn't appear to have an `onadvertisementreceived` event handler attribute.

In this specification that target appears to be the device object, although the [Web Bluetooth Scanning](https://webbluetoothcg.github.io/web-bluetooth/scanning.html#biblio-web-bluetooth) spec seems to extend that to fire at `navigator.bluetooth`... so it should probably also extend this attribute to be on more objects.

(I got here from w3ctag/design-reviews#333, though this issue isn't specific to the scanning spec so I'm filing it here.)

Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/426 using your GitHub account
Received on Monday, 4 February 2019 08:17:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 4 February 2019 08:17:55 UTC