Open wolenetz opened 3 years ago
Including the current mimetype+codecs string verbatim from the most recent of the addSourceBuffer() original call or possibly a more recent changeType() call in the introspection result could assist interoperable debugging.
This may also motivate getting the "track buffer" concept more clearly specified, especially if such an object model were made visible to apps via an introspection API.
This issue is part of a group of "introspection API" or similar API feature requests: #259, #209, #172, #40, #35.
A "SourceBuffer Introspection API" proposal was discussed at FOMS 2019 in October, but I don't currently find a spec issue tracking further discussion and potential inclusion in MSE v2, so I've filed this issue.
This API would enable greater ability to have precise interop tests, as well as give apps much more information about what is buffered so that they can workaround potential content or API implementation issues.
Comments welcome, especially: is this or something like this something which you would really want available in MSE? Are we missing your use case? Or is this feature unnecessary?
credit for the proposal: @sandersdan