- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Dec 2014 17:05:49 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27548 Bug ID: 27548 Summary: [MSE] Unspecified behavior when clients call endOfStream("decode'). Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions Assignee: adrianba@microsoft.com Reporter: jer.noble@apple.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org "If error is set to "decode" If updating equals true, then run the append error algorithm." If the client calls `mediaSource.endStream("decode");`, it is unspecified against which SourceBuffer should the algorithm run the Append Error Algorithm. (And in other cases, leads to weird implementation requirements, like the SourceBuffer having to tell the MediaSource which SourceBuffer is triggering the stream ended algorithm.) I propose the following changes: * The Append Error Algorithm will itself call the End Of Stream Algorithm. * The End of Stream Algorithm will no longer call the Append Error Algorithm. * The "run the end of stream algorithm" step be replaced by "run the append error algorithm" in the following places: * Byte Stream Formats * Segment Parser Loop * Initialization Segment Received * Coded Frame Processing -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 9 December 2014 17:05:54 UTC