Re: [whatwg/webidl] Fix `BufferSource` algorithms for shared and resizable buffers (PR #1529)

@MattiasBuelens pushed 9 commits.

6bca3d06ec4c65645c708c369dcb3125d4e69498  Define "out of bounds" before its call sites
ce397322f4cd7dd514c583028e2c1030b1b48e3f  Don't throw for out-of-bounds typed arrays in byte offset
bf628e6448b156191b4ba0835258402de6d3ecf1  Discriminate on [[DataView]] in byte length
8e7828f943e25188798b368a6e87b3f3579f3160  Assert that view is in bounds before writing
c8272d9b873d43e5bd1fe0b343e8a652f870c393  Simplify ArrayBuffer/transfer
b609e9519c13eb3a3f3cb65b2daab3bb43bdfcd3  Fix dangling realm references in transfer note
4f61d4de3137515ccf3e56edbe85e04a302cb7be  Document when reading a byte length or copying bytes throws
e7a1b9650a9dcd5ec7ca2c7473357e6e9e1bc8f2  Use plain "Assert:" steps
f0706c942257c88b60057fd9f151ec672eb4c2e0  Use scoped reference for BufferSource/byte length

-- 
View it on GitHub:
https://github.com/whatwg/webidl/pull/1529/changes/62016232ae42dcff49c6dce9a33ccd3da4fe80ae..f0706c942257c88b60057fd9f151ec672eb4c2e0
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1529/before/62016232ae42dcff49c6dce9a33ccd3da4fe80ae/after/f>