- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Feb 2016 15:55:58 +0000
- To: public-web-bluetooth-log@w3.org
@thegecko Right now, the spec only says to fire one, when the current Realm is disconnected "surprisingly", which happens either when the user revokes permission or when the device physically disconnects, but not when the Realm calls `.disconnect()`. (I could make `.disconnect()` also fire the event without changing anything significant.) This issue suggests to fire a second kind of `gattserverdisconnected`, when the device physically disconnects. We'd only actually see that if the user calls `.disconnect()`, since revocation would block it. But it sounds like we don't actually need this, since the user calling `.disconnect()` isn't a part of the protocol. -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/215#issuecomment-188851632 using your GitHub account
Received on Thursday, 25 February 2016 15:56:00 UTC