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

Anton Lundqvist via GitHub

• Re: [web-bluetooth] Service Worker support for WebBluetooth (#422) (Wednesday, 20 November)

Gordon Williams via GitHub

• Re: [web-bluetooth] Service Worker support for WebBluetooth (#422) (Tuesday, 19 November)

Jeffrey Yasskin via GitHub

• [web-bluetooth] new commits pushed by jyasskin (Monday, 4 November)

jgroc-de via GitHub

• Closed: [web-bluetooth] why no bluetooth "classic" (2.0/3.0) (#460) (Friday, 1 November)
• Re: [web-bluetooth] why no bluetooth "classic" (2.0/3.0) (#460) (Friday, 1 November)
• [web-bluetooth] why no bluetooth "classic" (2.0/3.0) (#460) (Friday, 1 November)

Jimmy Wärting via GitHub

• Re: [web-bluetooth] Use AbortController instead of stop method (#439) (Sunday, 17 November)

mduffy215 via GitHub

• Re: [web-bluetooth] Why does the Web Bluetooth Pairing Screen Show Multiple Entries for the Same Device? (#462) (Saturday, 9 November)
• [web-bluetooth] Why does the Web Bluetooth Pairing Screen Show Multiple Entries for the Same Device? (#462) (Saturday, 9 November)

Ovidio Ruiz-Henríquez via GitHub

• Re: [web-bluetooth] Service Worker support for WebBluetooth (#422) (Tuesday, 19 November)
• [web-bluetooth] Pull Request: Clarify availability permission relationship (Monday, 4 November)
• Re: [web-bluetooth] why no bluetooth "classic" (2.0/3.0) (#460) (Friday, 1 November)
• Re: [web-bluetooth] why no bluetooth "classic" (2.0/3.0) (#460) (Friday, 1 November)
• Re: [web-bluetooth] discussion: is there possibility to change getAvailability() be sync API (#459) (Friday, 1 November)

Reilly Grant via GitHub

• Re: [web-bluetooth] Why does the Web Bluetooth Pairing Screen Show Multiple Entries for the Same Device? (#462) (Sunday, 10 November)
• Closed: [web-bluetooth] Why does the Web Bluetooth Pairing Screen Show Multiple Entries for the Same Device? (#462) (Sunday, 10 November)

Yorkie Liu via GitHub

• Re: [web-bluetooth] Use AbortController instead of stop method (#439) (Monday, 18 November)

Last message date: Wednesday, 20 November 2019 13:26:23 UTC