youennf
youennf
https://w3c.github.io/mediacapture-fromelement/#dom-htmlcanvaselement-capturestream is pretty clear for canvas capture stream. "Content from a canvas that is not origin-clean MUST NOT be captured." The wording is less clear from video element tracks: "The...
I updated https://github.com/w3c/webrtc-pc/pull/2390 to leave some of the text. It seems the only case that could have cross origin MediaStreamTrack is video element capture. It seems best for the video...
> we should not mess with [[SendEncodings]] I agree with not changing [[SendEncodings]], but then we have descriptions that are not synchronised with [[SendEncodings]]. It seems rejecting in that case...
> This would make the internal behaviour of pipes visible Would it be fine if this would only be visible to a stream reader/writer for instance?
> * Store the previous chunk, and enqueue it when branch 2 (eventually) starts pulling. This chunk can be overwritten when branch 1 pulls in more chunks in the meantime....
Following on last meeting discussion, a potential approach would be something like: - Add a new type to ReadableStream/WritableStream/TransformStream, say 'transfer' - If type is 'transfer', we apply the API...
> There can be an arbitrary delay for queued writes to complete before A is "unhooked". That is an ergonomic issue: one calls postMessage, everything is fine so one navigates...
Great write up! Note that MediaStream/MediaStreamTrack have a clone method. Sure the underlying model is different but 'cloning a stream' is already in the air. Except if there are chances...
I agree with domenic, the benefit is to have fetch clone work as one would expect it to work. In terms of implementation, this should be pretty straightforward. See https://github.com/youennf/streams/commit/f56003da2bf564de22aeba0a1e61108958bd7aa5...