RE: Dealing with cues that come out of order

Apparently I overlooked this. It seems that the current spec requires the track processor in time order to sort the cues, so I think this is closed.

"The text track cues of a media element's text tracks are ordered relative to each other in the text track cue order, which is determined as follows: first group the cues by their text track, with the groups being sorted in the same order as their text tracks appear in the media element's list of text tracks; then, within each group, cues must be sorted by their start time, earliest first; then, any cues with the same start time must be sorted by their end time, latest first; and finally, any cues with identical end times must be sorted in the order they were last added to their respective text track list of cues, oldest first (so e.g. for cues from a WebVTT file, that would initially be the order in which the cues were listed in the file"

-----Original Message-----
From: John Foliot [mailto:john@foliot.ca] 
Sent: 31 January 2013 06:56
To: Sean Hayes; 'HTML Accessibility Task Force'
Subject: Dealing with cues that come out of order

Hi Sean,

I have been asked to reach out to you to get some feedback on the following:

http://www.w3.org/WAI/PF/HTML/track/actions/109

Can you tell us if bugs were filed, and/or has this issue been resolved? The Task Force is looking to clear out our backlog and it is unclear what we should be doing here.

Thanks for your prompt attention.

JF
---------------
John Foliot
Web Accessibility Specialist
W3C Invited Expert | Co-Facilitator, W3C HTML5 Accessibility Task Force
(Media)
Co-Founder, Open Web Camp

Received on Thursday, 6 June 2013 23:45:58 UTC