Kyle brought up a good point when reviewing bug 895091. Namely, that we should be able to observe ReadyState changes on the HTMLTrackElement. I've opened a spec bug for it here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23168. When/if the spec is updated we can go ahead and implement this.
From discussion on the spec bug -- there are 'load' and 'error' events that are fired at the track during the track processing model: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#start-the-track-processing-model So I'm thinking that this will probably be good for our needs.
Hi Rick, Can you give us the status of this bug? As of Firefox 28, the track element doesn't fire any events. Common events for this element include 'error', 'load' and 'cuechange'.
(In reply to G. C. Marty from comment #2) > Hi Rick, > Can you give us the status of this bug? As of Firefox 28, the track element > doesn't fire any events. > Common events for this element include 'error', 'load' and 'cuechange'. Sure, would be happy too. Most of the work to implement that functionality is going on in bug 882718. Those events happen as part of the time marches on algorithm so it maid sense for us to implement them together. This bug is more specifically about getting an 'onreadystatechange' event on the TrackElement, so that we can know more accurately when the ready state of a TrackElement changes.
I'm going to close this as I think 'load' and 'error' events on the TrackElement are enough for our needs. See the spec bug (https://www.w3.org/Bugs/Public/show_bug.cgi?id=23168) for more info. Development for the 'load' and 'error' events are going on in bug 882677 and the 'cuechange' event is being worked on in bug 882718.