bluetooth: Make errors from concurrent operations consistent |
||||||||
Issue descriptionPer https://github.com/WebBluetoothCG/web-bluetooth/issues/188#issuecomment-255121220, we raise a mix of NetworkErrors and NotSupportedErrors when the page runs connect, readValue, or writeValue in parallel. We should make them all consistent, and we should have the message explain what went wrong.
,
Jan 25 2017
,
Feb 3 2017
https://docs.google.com/document/d/1ClMet28ElV4VA4iRYG1fnIwmDcNk2mw8KrNHHC-QSjg/edit#
,
Apr 20 2017
Issues not modified in last 50 days aren't on track to ship in next release.
,
May 10 2017
Will come back to this as priorities allow.
,
Jun 7 2017
,
Jun 7 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by scheib@chromium.org
, Nov 5 2016