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 26459 - Should changing <track language> and company affect the TextTrack object?
Summary: Should changing <track language> and company affect the TextTrack object?
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-30 00:00 UTC by Ian 'Hixie' Hickson
Modified: 2014-09-09 21:15 UTC (History)
5 users (show)

See Also:


Attachments

Description Ian 'Hixie' Hickson 2014-07-30 00:00:46 UTC
Should changing <track language> and company affect the TextTrack object?

The spec currently says yes. There are no known use cases as far as I'm aware. It increases complexity a bit. On the other hand, cases where we have mutable attributes where mutating the attribute has no effect on the underlying data have resulted in some author confusion before (notably <script src>). If we changed this we'd also have to make the TextTrack object only get created on demand, since otherwise you could never set the language since the immutable TextTrack would be created before you had a chance to set the element's attributes. This would also break the way things work today when you move a <track> between <video> elements.

I think we're probably better off not changing any of this at this late stage.

This bug was split from bug 24563.
Comment 1 Philip Jägenstedt 2014-07-30 09:02:36 UTC
Yeah, the problem here is that there's no obvious time to create an immutable TextTrack object. On first access by a script won't be great, because then just printing it for debugging will have side effects...
Comment 2 Ian 'Hixie' Hickson 2014-07-30 20:52:13 UTC
Yeah, I think if we change this the only way to do it really would be to create the TextTrack object during media resource loading (or when the <track> is inserted, whichever happens last), and then create a new TextTrack if it's reused.

I've no idea if that would be Web-compatible. It's probably not worth finding out.
Comment 3 Philip Jägenstedt 2014-07-30 22:06:58 UTC
Do you mean so that the out-of-band tracks become available at the same time as in-band tracks? That doesn't sound too bad.

There's a Blink use counter for any VTTCue usage which gives some idea of risk:
http://www.chromestatus.com/metrics/feature/timeline/popularity/409

Any thoughts, Silvia or Simon?
Comment 4 Silvia Pfeiffer 2014-07-30 23:27:25 UTC
FWIW: I don't think it makes sense to change kind, srclang, label, id or default of a track.
Comment 5 Simon Pieters 2014-08-05 05:44:35 UTC
I don't like the idea of making <track>'s TextTrack not be available immediately. It seems like it makes it harder for authors to do things with it in script if you have to wait for the video's loadedmetadata event. For instance, a script might want to change the .mode of the TextTracks.
Comment 6 Ian 'Hixie' Hickson 2014-09-09 21:15:41 UTC
Given the discussion here I think this should be left as-is. I'm marking this WONTFIX. Please reopen if you think that's the wrong decision.