Chromium's implementations of Web Bluetooth and WebUSB currently throw a non-standard InvalidStateError when passed an ArrayBuffer or TypedArray which has been detached (e.g. by calling transfer() or using postMessage() to send the buffer through a MessagePort).
I expect this will not have any web compatibility impact because it is a programming error to pass a detached buffer to these APIs, which is why we added the exception to begin with. This change makes the APIs consistent with other buffer-consuming APIs like Web Serial and WebHID, where we handle this case with the specified behavior.