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 17139 - Consider making the argument optional for start() and end(). Many tutorials omit the argument, and think it means start of first range for start() and end of last range for end(). Maybe we should just make the API do what people expect.
Summary: Consider making the argument optional for start() and end(). Many tutorials o...
Status: RESOLVED WONTFIX
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: 2012-05-21 14:44 UTC by contributor
Modified: 2012-10-12 18:26 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-05-21 14:44:05 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html
Multipage: http://www.whatwg.org/C#time-ranges
Complete: http://www.whatwg.org/c#time-ranges

Comment:
Consider making the argument optional for start() and end(). Many tutorials
omit the argument, and think it means start of first range for start() and end
of last range for end(). Maybe we should just make the API do what people
expect.

Posted from: 85.227.154.145 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.3; U; en) Presto/2.10.229 Version/11.64
Comment 1 contributor 2012-07-18 17:33:01 UTC 
This bug was cloned to create bug 18176 as part of operation convergence.
Comment 2 Ian 'Hixie' Hickson 2012-07-26 07:20:38 UTC 
Wouldn't that just lead to scripts that fail badly when user agents support disjoint ranges?
Comment 3 Simon Pieters 2012-08-13 08:55:53 UTC 
I don't see how it would fail badly. Please elaborate?
Comment 4 Ian 'Hixie' Hickson 2012-10-03 16:47:55 UTC 
Well e.g. consider a case with seekable ranges 0..5, 10..15. The script wants to know if it can seek to 7. It checks the range without passing the arguments, and get 0..15. So it tries to seek to 7. But that won't work.
Comment 5 Simon Pieters 2012-10-04 07:11:15 UTC 
If you have discontinuous ranges, that means the server supports Range requests, so you can seek to 7.
Comment 6 Ian 'Hixie' Hickson 2012-10-12 18:26:02 UTC 
You're talking about .buffered ranges, I'm talking about .seekable ranges.

But .buffered ranges have the same problem. Suppose the page has detected that the user has gone offline (onoffline). Same ranges as above, but on .buffered instead of .seekable. Now if the page assumes it's one range, and yet seeks to the middle, it'll fail unexpectedly.