Re: [web-bluetooth] Question about mapping Scanning promises to Windows Bluetooth States (#531)

I would probably map RadioNotAvailable to NotSupportedError and ResourceInUse to InvalidStateError but otherwise these mappings seem reasonable. I'd say the implementation in Chromium probably maps more of these errors than it should to NetworkError.

GitHub Notification of comment by reillyeon
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 17 November 2020 01:42:12 UTC