WHATWG Streams have no [[owner]] but the spec sets it

[saschanaz]

Step 5 and 8 of https://www.w3.org/TR/webrtc-encoded-transform/#stream-creation sets [[owner]]:

3. Initialize this.[[readable]] to a new ReadableStream.
4. Set this.[[readable]].[[owner]] to this.

6. Initialize this.[[writable]] to a new WritableStream.

8. Set this.[[writable]].[[owner]] to this.

But there's no [[owner]] in https://streams.spec.whatwg.org/. What was the purpose of this?

[dontcallmedom]

a bit of archeology: the Streams spec used to have [[ownerReadableStream]] and [[ownerWritableStream]] internal slots, which were removed in whatwg/streams#1060 but probably were still in the mind of the editors when this notation was introduced in the spec 3 years ago

[youennf]

[[owner]] is used to enforce the constraint that the writable is given frames that were vended by the corresponding readable.

[youennf]

We could probably change this if needed be on using the streams sources instead.

[saschanaz]

[[owner]] is used to enforce the constraint that the writable is given frames that were vended by the corresponding readable.

Per my understanding, this spec only compares frame.[[owner]] in https://www.w3.org/TR/webrtc-encoded-transform/#abstract-opdef-writeencodeddata but not really the stream's [[owner]]. The latter is unused right now, so perhaps we can just remove it?

[alvestrand]

Note that this restriction has been questioned in #200 and removal has been proposed in #201.

[saschanaz]

Thanks, but I don't think the restriction uses stream's [[owner]] at all per #217 (comment). (And thus this shouldn't be blocked by #201.)

[youennf]

Yes, you are right, this does not seem to be used anymore given read/write encoded data are taking the rtcObject as parameter. We should remove it.