Question about mapping Scanning promises to Windows Bluetooth States

[usivagna]

In the scanning spec promises are rejected with either a TypeError, NotAllowedError, NotSupportedError, InvalidStateError or UnknownError. How would these errors map/overlap to error states in operating systems like Windows?

OS state		Description	Mapping to State in Scanning Spec
ConsentRequired	8	The operation requires consent.	NotAllowedError?
DisabledByPolicy	5	The operation is disabled by policy.	NotAllowedError?
DisabledByUser	7	The operation is disabled by the user.	NotAllowedError?
NotSupported	6	The operation is not supported on the current Bluetooth radio hardware.	NotSupportedError?
OtherError	4	An unexpected error has occurred.	UnknownError
RadioNotAvailable	1	The Bluetooth radio was not available. This error occurs when the Bluetooth radio has been turned off.	InvalidStateError?
ResourceInUse	2	The operation cannot be serviced because the necessary resources are currently in use.	UnknownError?
TransportNotSupported	9	The transport is not supported.	NotSupportedError?

[reillyeon]

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.