public-web-bluetooth-log@w3.org from February 2019 by author

Abhinandan via GitHub

• Re: [web-bluetooth] Can bluetooth objects be used after their originating document is refreshed? (#428) (Tuesday, 19 February)
• [web-bluetooth] Can bluetooth objects be used after their originating document is refreshed? (#428) (Monday, 18 February)
• Re: [web-bluetooth] Specify how re-connection works (#31) (Monday, 18 February)

Jeffrey Yasskin via GitHub

• [web-bluetooth] new commits pushed by jyasskin (Tuesday, 12 February)

L. David Baron via GitHub

• [web-bluetooth] there's no onadvertisementreceived event handler attribute (#426) (Monday, 4 February)

Reilly Grant via GitHub

• Re: [web-bluetooth] Can bluetooth objects be used after their originating document is refreshed? (#428) (Tuesday, 19 February)
• Re: [web-bluetooth] Specify how re-connection works (#31) (Monday, 18 February)
• Re: [web-bluetooth] Can bluetooth objects be used after their originating document is refreshed? (#428) (Monday, 18 February)
• Closed: [web-bluetooth] Can bluetooth objects be used after their originating document is refreshed? (#428) (Monday, 18 February)
• Closed: [web-bluetooth] Missing onadvertisementreceived attribute on Bluetooth and BluetoothDevice (#426) (Tuesday, 12 February)
• [web-bluetooth] Pull Request: Add 'onadvertisementreceived' attribute to BluetoothDeviceEventHandlers (Tuesday, 12 February)
• Re: [web-bluetooth] there's no onadvertisementreceived event handler attribute (#426) (Monday, 4 February)

russellrain via GitHub

• Re: [web-bluetooth] Should connectGATT() time out or wait until a device is available? (#152) (Monday, 4 February)

Last message date: Tuesday, 19 February 2019 10:46:33 UTC