Bug 61817
| Summary: | video-play-stall.cgi needs to pretend to support range requests | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Steve Lacey <sjl> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Steve Lacey
http/tests/video-video-seekable-stall.html stalls the video download (by using video-play-stall.cgi and then requests a range via the 'seekable' attribute.
Unfortunately, as the script doesn't support range requests, chromium thinks that the media is streaming and can't provide a TimeRanges in response to the request. The spec kinda backs this up as not been needed (from http://www.w3.org/TR/html5/video.html#dom-media-seekable):
"If the user agent can seek to anywhere in the media resource, e.g. because it is a simple movie file and the user agent and the server support HTTP Range requests, then the attribute would return an object with one range, whose start is the time of the first frame (the earliest possible position, typically zero), and whose end is the same as the time of the first frame plus the duration attribute's value (which would equal the time of the last frame, and might be positive Infinity)."
Which seems to imply that the range should be returned if range requests are supported.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Steve Lacey
video-seekable-stall has been deleted.