17139 2012-05-21 14:44:05 +0000 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. 2012-10-12 18:26:02 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#time-ranges P3 normal Unsorted 1 contributor ian ian mike zcorpan contributor oldest_to_newest 67967 0 contributor 2012-05-21 14:44:05 +0000 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 70819 1 contributor 2012-07-18 17:33:01 +0000 This bug was cloned to create bug 18176 as part of operation convergence. 71496 2 ian 2012-07-26 07:20:38 +0000 Wouldn't that just lead to scripts that fail badly when user agents support disjoint ranges? 72110 3 zcorpan 2012-08-13 08:55:53 +0000 I don't see how it would fail badly. Please elaborate? 75237 4 ian 2012-10-03 16:47:55 +0000 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. 75295 5 zcorpan 2012-10-04 07:11:15 +0000 If you have discontinuous ranges, that means the server supports Range requests, so you can seek to 7. 76144 6 ian 2012-10-12 18:26:02 +0000 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.