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 12186 - <video> Should explicitly state that TimeRanges.end() is inclusive, so that if the browser reverts to HAVE_METADATA while playing, the .buffered.end(0) value is the last rendered frame, and .currentTime is the next frame, and so that when .ended
Summary: <video> Should explicitly state that TimeRanges.end() is inclusive, so that i...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-25 15:34 UTC by contributor
Modified: 2011-08-04 05:00 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-02-25 15:34:45 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#timeranges

Comment:
Should explicitly state that TimeRanges.end() is inclusive, so that if the
browser reverts to HAVE_METADATA while playing, the .buffered.end(0) value is
the last rendered frame, and .currentTime is the next frame, and so that when
.ended is true, .buffered.end(0) equals .currentTime..

Posted from: 76.102.14.57 by ian@hixie.ch
Comment 1 Ian 'Hixie' Hickson 2011-06-03 00:23:13 UTC 
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: Concurred with reporter's comments.
Comment 2 contributor 2011-06-03 00:24:11 UTC 
Checked in as WHATWG revision r6180.
Check-in comment: Explicitly say that ranges are inclusive.
http://html5.org/tools/web-apps-tracker?from=6179&to=6180
Comment 3 Michael[tm] Smith 2011-08-04 05:00:28 UTC 
mass-moved component to LC1