W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2011

[Bug 10723] <video> Support stopping at the time given by a media resource's fragment identifier

From: <bugzilla@jessica.w3.org>
Date: Tue, 10 May 2011 07:34:39 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QJhSp-0002a1-T9@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723

--- Comment #19 from Philip Jägenstedt <philipj@opera.com> 2011-05-10 07:34:39 UTC ---
(In reply to comment #18)
> Some clarifications:
> 
> (In reply to comment #17)
> > (In reply to comment #15)
> > > 
> > > 2.
> > > Also this site:
> > > http://metavid.org/w/index.php?title=Stream:senate_proceeding_02-04-11/0:00:25/0:01:45&tl=1
> > 
> > This again seems to just be one media file with jumping to different segments.
> > You wouldn't want to replace the URL on the fly, that would trigger a file
> > reload each time.
> 
> No it doesn't. Browsers have stopped reloading resources where just the
> fragment is changed and not the actual resource URL. The way in which media
> fragment URIs are specified plays with that fact, too. Unless the resource has
> expired, it will only request the appropriate byte ranges for the time range
> specified in the URL. 

Which browsers? Is the special-casing when the src attribute is set, or is it
part of the resource selection algorithm (which is run asynchronously as a
result of setting src)?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 10 May 2011 07:34:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:10 UTC