Re: [web-bluetooth] Handling readValue from protected/secure characteristics of not-yet-PIN-paired devices is underspecified (#563)

I think the specification does provide sufficient language here as the steps for handling errors include attempting to pair before retrying the operation, as Chromium now does. I think it can be considered an implementation bug that on a platform (Windows) which otherwise supports multiple parallel calls to methods like `readValue()` it does not support parallel requests for pairing. I'll add a note referencing this issue to [Chromium issue 960258](https://bugs.chromium.org/p/chromium/issues/detail?id=960258). If you agree we can close this issue.

-- 
GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/563#issuecomment-942764356 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 13 October 2021 22:21:53 UTC