Wondering if not setting byteOffset=0 in the TypedArray.subarray for detached buffers is a spec omission or a deliberate design decision.
I had noticed a new test262 for it in built-ins/TypedArray/prototype/subarray/byteoffset-with-detached-buffer.js and indeed the spec seems to require reading the byteOffset even if the buffer is detached.
If the array is detached spec says 6. If IsTypedArrayOutOfBounds(srcRecord) is true, then Let srcLength be 0.. IsTypedArrayOutOfBounds() considers a detached array out of bounds, so that takes effect and srcLength=0, however further below we don't do the same with the srcByteOffset. That seems inconsistent at first sight. Why does it make sense to preserve the byteOffset from a detached buffer; is it deliberate or it's a spec omission?
It would seem that If IsTypedArrayOutOfBounds(srcRecord) is true, then Let srcByteOffset be 0 would be more reasonable to have.