Bugzilla

Thanks for the context. I think the issue is that in terms of *WebIDL* types a WebIDL `ArrayBufferView` type can't contain a WebIDL `undefined` value, regardless of conversions. So it seems to me that the Streams spec has a bug here. If after conversion to EcmaScript an actual `value` property with value `undefined` is needed here, then the Streams spec could allow for undefined by making the value property a union of `ArrayBufferView or undefined` (and yes Kagami, I haven't forgotten about bug 1659158! :-))

I'll note that for EcmaScript->WebIDL conversions an EcmaScript `undefined` value for a property means that the entry is missing in the WebIDL dictionary, so the end result is the same as not having that property at all.

Thanks for the context. I think the issue is that in terms of *WebIDL* types a WebIDL `ArrayBufferView` type can't contain a WebIDL `undefined` value, regardless of conversions. So it seems to me that the Streams spec has a bug here. If after conversion to ECMAScript an actual `value` property with value `undefined` is needed here, then the Streams spec could allow for undefined by making the value property a union of `ArrayBufferView or undefined` (and yes Kagami, I haven't forgotten about bug 1659158! :-))

I'll note that for ECMAScript->WebIDL conversions an ECMAScript `undefined` value for a property means that the entry is missing in the WebIDL dictionary, so the end result is the same as not having that property at all.