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 22246 - media.buffered should have length 0
Summary: media.buffered should have length 0
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-03 15:02 UTC by Dominique Hazael-Massieux
Modified: 2013-08-27 08:56 UTC (History)
2 users (show)

See Also:

Attachments

Description Dominique Hazael-Massieux 2013-06-03 15:02:37 UTC 
The HTML5 spec says:
"The buffered attribute must return a new static normalized TimeRanges object that represents the ranges of the media resource, if any, that the user agent has buffered"
http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0.html#dom-media-buffered

This suggests to me that when no range have been buffered, no TimeRanges should be returned, and thus media.buffered should have zero length (and thus no need to define what .start() and .end() do on it)
Comment 1 Harald Alvestrand 2013-08-27 08:56:15 UTC 
Resolved in 20130824 version of MediaCapture.