- From: MikeTheDane via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 May 2020 00:23:39 +0000
- To: public-web-bluetooth-log@w3.org
The Bluetooth specification specifies that the DEVICE should throw the NotSupportedError error over the link when an unsupported GATT request is received. It does not specify, nor should it specify, how that is communicated to upper layers on the peer device or what action to take when this error occurs. I strongly believe that Web Bluetooth should specify writeValue() as an obsolete method that should not be used in new implementations due to the inconsistent behavior on various platforms. Changing the behavior of writeValue() in ANY way would completely remove the need to keep it - which is to ensure backward compatibility. I would even suggest that the method is retired after a certain period of time (leave it after this time, but remove it from the documentation). On Thu, Apr 30, 2020 at 3:28 PM Ovidio Ruiz-Henríquez < notifications@github.com> wrote: > That's one reason that the specification should declare what algorithm > writeValue() should use. That would clear up any confusion on how this > API is implemented for both users and implementors. > > As for the error, the algorithm for write value currently specifies that > in that scenario, NotSupportedError should be thrown. So it looks like > that's a bug for Chromium's implementation using BlueZ. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/WebBluetoothCG/web-bluetooth/issues/238#issuecomment-622150346>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACNNFKJDBMXCEA6PVGL465DRPH3QTANCNFSM4CC422ZQ> > . > -- GitHub Notification of comment by MikeTheDane Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/238#issuecomment-622188463 using your GitHub account
Received on Friday, 1 May 2020 00:23:42 UTC