This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#perform-automatic-text-track-selection Complete: http://www.whatwg.org/c#perform-automatic-text-track-selection Comment: <track> Only set one default track to showing Posted from: 94.234.170.175 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.4; U; en) Presto/2.10.289 Version/12.02
[[ Otherwise, if there are any text tracks in candidates that correspond to track elements with a default attribute set whose text track mode is set to disabled, then set the text track mode of each such track to showing. ]] We don't want to implement this in Opera. I think it would result in a bad user experience when the author has screwed up. Consider: The author has set a user pref for automatic track selection, and goes on to test his page in his browser. He sees that only one track is enabled by default, and is happy with the result, so publishes the page. Users who also have a pref set get the same experience, but users who don't have a pref set or have a pref but it doesn't match any of the available tracks, get all the default="" tracks showing (which might well be all tracks). Usually we try hard not to punish users when authors screw up. In this case the author doesn't even notice that he has screwed up. Instead we want this step to say that the first <track> with a default attribute should be set to showing. We think excess default tracks, both in the user pref case and the default="" case, should be *disabled*, not hidden, since hidden means we have to fetch and process them which hurts perf if the author isn't going to use them anyway. metadata should be special-cased as follows: user pref does not apply at all; all default tracks get set to hidden.
Please file a separate bug for the default="" tracks when there's a user preference that enables something else, if you want that examined. (The current requirement is intentional: it's based on the assumption that authors will assume in JS that tracks marked default="" will always load — which they almost always will — so as to avoid bugs when the user has set a preference.) I'll change the default="" behaviour to only enabling the first default track from each batch, and change metadata tracks to not go through the preferences mechanism and just enable all default tracks for those, always.
Checked in as WHATWG revision r7350. Check-in comment: Only enable the first default text track, not all of them, except for metadata. For metadata, remove the user preference logic and just always enable them. http://html5.org/tools/web-apps-tracker?from=7349&to=7350