This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
While we have a lot of special events for adding/removing tracks and cuechange/cueexit/cueenter. We do not have an event for the case, where a user changes the mode of a track. This is for example needed for custom styleable controls. If the user changes the mode using the context menue from showing/disabled to disabled/showing we need an event for this to update for example the visual state of our controls.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no change needed Rationale: The "onchange" event is called on the TextTrackList when this happens. Exact text is: " Whenever a text track that is in a media element's list of text tracks has its text track mode change value, the user agent must run the following steps for the media element: If the media element's pending text track change notification flag is set, abort these steps. Set the media element's pending text track change notification flag. Queue a task that runs the following substeps: Unset the media element's pending text track change notification flag. Fire a simple event named change at the media element's textTracks attribute's TextTrackList object. If the media element's show poster flag is not set, run the time marches on steps. " See in http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#timed-text-tracks