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 26022 - The example after paragraph 9 should not say "nearest key frame" but "nearest key frame in the appropriate direction" (because of the constraints in paragraph 9).
Summary: The example after paragraph 9 should not say "nearest key frame" but "nearest...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-09 21:02 UTC by contributor
Modified: 2014-08-27 00:03 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-06-09 21:02:18 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html
Multipage: http://www.whatwg.org/C#seeking
Complete: http://www.whatwg.org/c#seeking
Referrer: http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CB8QFjAA&url=http%3A%2F%2Fwww.whatwg.org%2Fspecs%2Fweb-apps%2Fcurrent-work%2Fmultipage%2Fthe-video-element.html&ei=LByWU4_tNoztoASq24JQ&usg=AFQjCNEn_4tBy_EiK9CWL-FC7-ofUcBrnA&sig2=eUVx53kDReRcQLFMc9fBeQ&bvm=bv.68693194,d.cGU&cad=rja

Comment:
The example after paragraph 9 should not say "nearest key frame" but "nearest
key frame in the appropriate direction" (because of the constraints in
paragraph 9). 

In paragraph 11, "the given" should be "the given (or adjusted)" because
paragraph 9 can adjust the position.

And the 3rd note after paragraph 11 seems wrong. You don't really mean "does
not get updated asynchronously" do you? You certainly don't seem to mean "does
get updated synchronously". Probably want to be explicit here with something
like "Note that the currentTime attribute returns the official playback
position, not the current playback position, so the value of the currentTime
attribute does not change until the media element reaches a stable state in
step 13"

Posted from: 66.114.38.252
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Firefox/31.0
Comment 1 Ian 'Hixie' Hickson 2014-08-27 00:02:45 UTC 
Fixed.

Fixed.

I actually did mean "asynchronously" — the currentTime is only ever updated synchronously, during the event loop logic. (The industry seems to have damaged the words "synchronous" and "asynchronous" relative to their dictionary meanings.) But I've clarified it anyway.
Comment 2 contributor 2014-08-27 00:03:31 UTC 
Checked in as WHATWG revision r8721.
Check-in comment: Clarify seeking
http://html5.org/tools/web-apps-tracker?from=8720&to=8721