This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section affected: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#playing-the-media-resource In the current cue processing algorithm, a cue whose start time is equal to the end time never gets into "current cues", which is defined as the list of cues "whose start times are less than or equal to the current playback position and whose end times are greater than the current playback position". However, certain kinds of cues (e.g., extended video descriptions which pause the playback while presenting a description) require such a zero-duration cue as the media timeline is defined based on the timeline of the original media resource. The algorithm should activate even a zero-duration cue at the specified time. Once the cue is activated and the corresponding event is fired, the system or a script will be able to handle it (e.g., pause/resume the playback in the case of extended descriptions). A use case of extended descriptions is found at: http://media.w3.org/2010/08/
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: Accepted Change Description: see diff given below Rationale: Agreed that zero-length cues should have events fired. In fact all cues should have events fired, even if the browser is skipping them due to high load.
Checked in as WHATWG revision r6517. Check-in comment: Make browsers fire events for all cues, even when they're overloaded, rather that skipping events on skipped cues. http://html5.org/tools/web-apps-tracker?from=6516&to=6517