This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26659 - [InbandTracks] no definition for "text track in-band metadata track dispatch type"
Summary: [InbandTracks] no definition for "text track in-band metadata track dispatch ...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Sourcing In-band Media Resource Tracks (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 25133
  Show dependency tree / graph
 
Reported: 2014-08-25 21:11 UTC by Ian 'Hixie' Hickson
Modified: 2014-10-15 10:13 UTC (History)
4 users (show)

See Also:

Attachments

Description Ian 'Hixie' Hickson 2014-08-25 21:11:50 UTC 
The spec doesn't say how to set the text track in-band metadata track dispatch type. Precise rules for doing so are in the HTML spec, but it seems like it should probably be moved to this spec?
Comment 1 Silvia Pfeiffer 2014-08-30 14:04:16 UTC 
Makes sense to me.
We would move http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content.html#steps-to-expose-a-media-resource-specific-text-track point 4 over into the new spec.
Comment 2 Bob Lund 2014-09-19 19:58:48 UTC 
Added the rules for setting inBandMetadataTrackDispatchType [1]. There was discrepancy for Ogg between W3C and WHATWG. I think the use of the Role header is correct.

Created PR #18.

[1] http://rawgit.com/boblund/HTMLSourcingInbandTracks/bug26659/index.html
Comment 3 Silvia Pfeiffer 2014-09-22 07:26:07 UTC 
Good catch,  yeah, 'Role' is more appropriate for Ogg, in particular since 'Name' is already represented in the 'ID'.
Comment 4 Bob Lund 2014-10-14 21:37:37 UTC 
(In reply to Silvia Pfeiffer from comment #3)
> Good catch,  yeah, 'Role' is more appropriate for Ogg, in particular since
> 'Name' is already represented in the 'ID'.

This should be marked Resolved. I can go through the open bugs and do that for those I think are fixed if you'd like
Comment 5 Silvia Pfeiffer 2014-10-15 10:13:00 UTC 
Since pull request #18 is merged, you can just close this.
Whenever one of my pull requests got merged, I go back and close the associated bug.