This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Update the SourceBuffer.appendStream() stream parameter to be a ReadableByteStream instead of a Stream. Update all related algorithms and update the Streams API spec reference.
Change committed... https://github.com/w3c/media-source/commit/502f28af99d3d38923a109c824f3a284062d7135 Updated appendStream() to use ReadableStream for now since the W3C streams spec doesn't even have a class definition for ReadableByteStream.
The current status of this bug is that we are waiting for the dust to settle from https://github.com/whatwg/streams/issues/253 and for the ReadableByteStream stuff to move from https://github.com/whatwg/streams/blob/master/BinaryExtension.md into the main Streams spec so that it can be linked to from MSE. I reached out to Domenic and Takeshi about a week or 2 ago and it sounded like they expected this to be done in the next few weeks. Once the Streams API work is done, then the MSE spec needs to be reworked to use the current incarnation of the API. The MSE spec also needs to make sure it uses whatever Streams mechanisms are available to guarantee that it becomes the exclusive reader of the stream. We definitely want appendStream() operations to block JS read access while the append is occuring to avoid non-deterministic behavior.
(In reply to Aaron Colwell from comment #2) > The current status of this bug is that we are waiting for the dust to settle > from https://github.com/whatwg/streams/issues/253 and for the > ReadableByteStream stuff to move from > https://github.com/whatwg/streams/blob/master/BinaryExtension.md into the > main Streams spec so that it can be linked to from MSE. I reached out to > Domenic and Takeshi about a week or 2 ago and it sounded like they expected > this to be done in the next few weeks. > > Once the Streams API work is done, then the MSE spec needs to be reworked to > use the current incarnation of the API. The MSE spec also needs to make sure > it uses whatever Streams mechanisms are available to guarantee that it > becomes the exclusive reader of the stream. We definitely want > appendStream() operations to block JS read access while the append is > occuring to avoid non-deterministic behavior. https://github.com/whatwg/streams/issues/253 is now marked as closed. Do we know when ReadableByteStream will move in the main Streams spec? /paulc
(In reply to Paul Cotton from comment #3) > https://github.com/whatwg/streams/issues/253 is now marked as closed. > > Do we know when ReadableByteStream will move in the main Streams spec? > Apparently the master Stream issue for the implementation of the ReadableByteStream is: https://github.com/whatwg/streams/issues/300 See Domenic's reply to my query at: https://github.com/whatwg/streams/issues/253#issuecomment-91706806 /paulc
Is appendStream() really the best name here? This is a one-off operation, no? Append sounds like the underlying object has a list of streams.
(In reply to Paul Cotton from comment #4) > (In reply to Paul Cotton from comment #3) > > https://github.com/whatwg/streams/issues/253 is now marked as closed. > > > > Do we know when ReadableByteStream will move in the main Streams spec? > > > > Apparently the master Stream issue for the implementation of the > ReadableByteStream is: > https://github.com/whatwg/streams/issues/300 > > See Domenic's reply to my query at: > https://github.com/whatwg/streams/issues/253#issuecomment-91706806 > > /paulc And now see Takeshi Yoshino's reply. ETA for integration is now week of Apr 20: https://github.com/whatwg/streams/issues/253#issuecomment-92841148 /paulc
In the meantime, we should add an Issue box to the appendStream() algorithm that indicates that it is not final and is subject to change. This is especially important MSE is in CR and presumably stable. There was support for this at the f2f.
(In reply to David Dorwin from comment #7) > In the meantime, we should add an Issue box to the appendStream() algorithm > that indicates that it is not final and is subject to change. This is > especially important MSE is in CR and presumably stable. There was support > for this at the f2f. We can now reference https://streams.spec.whatwg.org/#rbs for the definition of ReadableByteStream in the Streams spec. For reference see https://github.com/whatwg/streams/issues/253#issuecomment-99877403 /paulc
This bug has been migrated to the GitHub issue tracker. Please follow/update progress using the GitHub issue: https://github.com/w3c/media-source/issues/14