W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2007

[whatwg] minor comments on media element cue ranges

From: Dave Singer <singer@apple.com>
Date: Wed, 31 Oct 2007 17:12:36 +0100
Message-ID: <p0624081bc34e588ddae2@[10.10.11.15]>
"When the current playback position of a media element changes (e.g. 
due to playback or seeking), the user agent must run the following 
steps. If the current playback position changes while the steps are 
running, then the user agent must wait for the steps to complete, and 
then must immediately rerun the steps. (If one iteration takes a long 
time, this can cause certain ranges to be skipped over as the user 
agent rushes ahead to "catch up".) "

Perhaps the parenthesized comment could be prefixed:  (These steps 
are taken as often as possible or needed;  if one iteration takes a 
long time, ...)?  Just a thought.

"3.	If none of the cue ranges in current ranges have their 
"active" boolean set to "false" (inactive) and none of the cue ranges 
in current ranges have their "active" boolean set to "true" (active), 
then abort these steps. "

one rather suspects that "other ranges" is  intended for the second test?

"5.	If there are any cue ranges in other ranges that have their 
"active" boolean set to "true" (active) and have their "pause" 
boolean set to "true" as well, then immediately act as if the 
element's pause() method had been invoked. "

Does the pause boolean add much over the exit handler?  It seems that 
if the exit is because of a seek, it might be kinda odd to 
immediately pause again?

-- 
David Singer
Apple/QuickTime
Received on Wednesday, 31 October 2007 09:12:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:37 UTC