- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Feb 2025 21:32:12 +0000
- To: public-web-bluetooth-log@w3.org
Overall I'm supportive of this however given that Web Bluetooth has been deployed for many years it would take some investigation to determine whether the ArrayBuffers it exposes ([`BluetoothRemoteGATTCharacteristic.value`](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothremotegattcharacteristic-value) being the most obvious example) can be made immutable without affecting compatibility. For the most part, as @jyasskin mentioned, edits to the buffer by script can be effectively ignored by the implementation because it only ever writes to the buffer. Reading back over the Scanning API I'm not sure why it was necessary to use an ArrayBuffer in a way that would make script modifications relevant and the spec could be modified to remove this ambiguity completely. It think this matters more to specs like WebGPU and WebNN where it is useful to model an immutable memory region because the underlying platform requires it (e.g. a device buffer which is mapped read-only). -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/300#issuecomment-2666972937 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 February 2025 21:32:12 UTC