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

[Bug 12643] <video> change of fragment in media fragment URI consequences

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Aug 2011 06:50:05 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qr2c9-0000QQ-Pl@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12643

RaphaŽl Troncy <raphael.troncy@eurecom.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #10 from RaphaŽl Troncy <raphael.troncy@eurecom.fr> 2011-08-10 06:50:04 UTC ---
Ian,

It seems you haven't paid much attention to what is discussed in this thread.
You write:
  "If you don't want to reload the file, don't change the URL. That's
  what changing the URL does for pretty much every similar feature in HTML."
but we are talking of changing only the fragment part of the URL not the full
URL. When you change the fragment of an HTML document, the immediate result is
to scroll to another section of this document and certainly not to reload the
whole resource. The question raised in his thread is: what should a change from
http://example.com/video.ogv#t=20 to http://example.com/video.ogv#t=50 do when
this url is the src of a <video> element?

Perhaps this is a non-problem as Philip and Chris have argued earlier: at some
point the fragment URI part is being interpreted (in fact: point 8 in
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#getting-media-metadata)
and we should just specify that
the user agent will jump to that point when changing the fragment on the URI. I
would like a confirmation that the resource selection algorithm is sufficiently
described for this. But your current response is just not relevant.

-- 
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 Wednesday, 10 August 2011 06:50:11 UTC

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