This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11453 - The timeupdate event should distinguish normal play
Summary: The timeupdate event should distinguish normal play
Status: CLOSED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 14:14 UTC by Sean Hayes
Modified: 2011-08-04 05:12 UTC (History)
5 users (show)

See Also:


Attachments

Description Sean Hayes 2010-12-02 14:14:57 UTC
The timeupdate event fired by media events should have a means for the handler to distinguish whether the event was caused "as part of normal playback" or "in an especially interesting way, for example discontinuously".

The author may need to prevent linked activities (particularly those that have a duration, such as triggering an audio sound) when not in normal playback mode. Conversly authors may need to apply overlays (e.g. chapter descriptions)when the user is scrbbing the timeline which would not be revealed during normal play.
Comment 1 Philip J├Ągenstedt 2010-12-03 09:00:41 UTC
Can you explain the use case in a bit more detail? Why isn't the seeking event enough to detect discontinuity? That's what I did to emulate the TimedTrack interface in <http://people.opera.com/philipj/2010/10/02/ovc/demos/track.js>, modulo a hack to make timeupdate trigger more often than what the spec requires.
Comment 2 Michael[tm] Smith 2011-08-04 05:12:25 UTC
mass-move component to LC1