|18933||Segment byte boundaries are not defined||ASSIGNED||Assigned to Mark to work with Steven on text updates.|
|18922||Add a parser free, codec agnostic example||RESOLVED NEEDSINFO||If Haakon provides the example then we can discuss adding.|
|18921||append(data) should accept any part of media segment ||RESOLVED WONTFIX||The current goals of the API require that applications do have an accurate offset of all segments. Applications are likely to compose presentations from multiple sources and need to understand how to map these together.|
|18920||addSourceBuffer parameter type should be optional||RESOLVED WONTFIX||Discussed previously during the call. Current consensus is to leave the type parameter to allow user agents to fail fast if they choose.|
|18642||Handle timestamp overflow in append(data)||ASSIGNED||Assigned to Aaron. Next action is to reorganise the |
append() algorithm to make it more precise.
|18615||Define how SourceBuffer.buffered maps to HTMLMediaElement.buffered||ASSIGNED||Assigned to Aaron to work with Philip to remove any ambiguity.|
|18592||How much is "enough data to ensure uninterrupted playback"||NEW||YES||This topic requires more review and discussion to better align the content model for MSE with HTML5.|
|18575||Section 2. Source Buffer Model should be non-normative||ASSIGNED||YES||This is a LARGE change to the structure of the document to more clearly separate normative and informative language. Assigned to Aaron.|
|18601||Contradictory requirements for initialization segments||ASSIGNED||YES||Discussed previously during the call. Current proposal is to remove the text making initialization segments optional.|
|18587||Define clearly what data is removed when setting an explicit duration||ASSIGNED||Resolution of this bug is dependent on the |
SourceBuffer.remove modification in bug 18709.
|18400||Define and document timestamp heuristics ||ASSIGNED||Next step: reorganize |
append() description into sub-algorithms in order to introduce this proposal. This reorganisation work is captured in bug 18462.
|18960||Define how AudioTrack.id & VideoTrack.id are generated||NEW||YES||This topic needs more discussion to conclude how to handle track IDs. Feedback from the wider WG might be helpful to ensure alignment with HTML5 media elements.|
|19531||simplify MIME type capability detection ||NEW||YES||We will clarify that supporting MSE a subset of the formats the media element supports is acceptable to allow staged implementation. We need a little more review and discussion about the exact mechanism/method.|
|18963||Provide a mechanism for rate limiting appending ||NEW||YES||We should discuss whether this is required for v1.|
|18962||Allow appending with XHR||NEW||YES||We discussed this on the call recently. Current proposal is |
void appendStream(Stream). We need to discuss whether the any new mechanisms are required to indicate progress/completion. Also need to resolve how Stream support will be added to W3C XHR with WebApps.
|18709||Add SourceBuffer.remove() method||NEW||YES||We need to review to confirm consensus before making the change proposed in the bug.|
|17006||<track> Setting track language & kind when the information is in a manifest||ASSIGNED||YES||Assigned to Adrian to make a proposal before TPAC for discussion.|
|17002||Specify a mechanism to determine which SourceBuffer an AudioTrack,VideoTrack, or TextTrack belong to.||NEW||YES||Should be simple to address but we need to discuss once we resolve bug 18960.|
|17000||Define a capability detection mechanism||RESOLVED LATER||We should wait for more implementation experience to see if we really need a programmatic mechanism for determining capabilities. Resolved LATER. Bug 19531 covers the format support aspect.|
|17094||Define segment formats for MPEG2-TS||ASSIGNED||YES||This needs more review and discussion. We want to discuss at TPAC if there are enough people with domain knowledge. Goal is to get agreement on text by the end of TPAC that we can add into the spec as a starting point for refinement.|