[Bug 26718] [InbandTracks] Container information vs. Manifest information

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26718

--- Comment #8 from Bob Lund <b.lund@cablelabs.com> ---
(In reply to Jon Piesing (HbbTV) from comment #7)
> I think there are significant drawbacks to what is proposed here.
> 
> While it could make sense for representations that are currently being
> presented, it would seem to force the UA to actually fetch the data for
> representations that are not being presented in order to populate the
> properties.

The proposed resolution only addresses the priority the UA should use in
sourcing in-band tracks - data in media container, then MPD. So, it doesn't
require the UA to do anything new with respect to sourcing tracks.

I think the point you are raising has to do with when the UA needs to source
Cues in the text tracks. This is a valid point and applies to other media
containers besides DASH. We could specify that text tracks should be created
with @mode set to "disabled" [1]. In this mode, the track object exists in the
DOM but no Cues are created.

But, this is a separate issue that has nothing to do with this bug. I will
create a new bug to track this.

[1] http://www.w3.org/TR/html5/embedded-content-0.html#text-track-disabled

> 
> Was this case considered?
> 
> Apologies for not reacting earlier but I've been on vacation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 23 September 2014 19:38:43 UTC