Repository navigation
buffer: isUtf8 and isAscii accept detached TypedArray views #64503
Description
Activity
It's not obvious this is a bug. In both cases, the detached
ArrayBufferjust comes back as zero-length. These APIs handle zero-length just fine (e.g.isUtf8(new Uint8Array(0))).I do see that the docs say "Throws if the
inputis a detached array buffer" but I kind of view that as a doc error rather than an implementation error.We also only check the
detached_property in these two methods AFAICT, all other uses of ABVC in the Buffer API just treat detached buffers as zero-length, including other string-encoding operations likeBuffer.prototype.toString(). I'm ±0 on whether we should be erroring with detached backing ArrayBuffers, but it should be consistent imoOk, the implementation behavior is a bit inconsistent. I would suggest that the final
isUtf8(transferedArrayBuffer)should just returntrue, being treated as a zero-length.- added a commit that references this issue
on Aug 5, 2026 - added a commit that references this issue
on Aug 13, 2026 - added 2 commits that reference this issue
on Aug 25, 2026
Version
latest main branch
Platform
Subsystem
buffer
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
ArrayBufferViewContents reads the view's zero byte length but does not record the detached state of its backing ArrayBuffer.
What is the expected behavior? Why is that the expected behavior?
Both functions should throw ERR_INVALID_STATE, consistent with passing a detached ArrayBuffer directly.
What do you see instead?
Both functions return true.
Additional information