W3C home > Mailing lists > Public > public-media-fragment@w3.org > September 2010

Re: minutes of 2010-09-08 teleconference

From: Jack Jansen <Jack.Jansen@cwi.nl>
Date: Thu, 9 Sep 2010 21:29:50 +0200
Cc: RaphaŽl Troncy <raphael.troncy@eurecom.fr>, Erik Mannens <erik.mannens@ugent.be>, public-media-fragment@w3.org
Message-Id: <F31BEFD5-CDB9-4B9A-A283-B515009DAEE5@cwi.nl>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>

On 9 sep 2010, at 15:27, Silvia Pfeiffer wrote:

> Can Ian provide a pointer to a paragraph in any of the HTML spec (including the HTML5 current draft) where it is written that a browser MUST jump to the section identified by a (resolvable) frag id for an HTML document? This is the standard behavior in all browsers, right? However, I cannot find where it has ever been written ... Why would this be different for media resources?
> 
> It's here: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#scroll-to-fragid
> It had to be included because the specification of what to do with fragment identifiers in URLs to text/html resources should have been in http://www.ietf.org/rfc/rfc2854.txt, but isn't.

Silvia,
that last sentence again seems to indicate that the html-folks assume that specifying the behaviour of fragments in an HTML context is the responsibility of whoever defines the URL format. This strikes me as counter-intuitive, as I've already explained in response to the mail about MF-semantics.

As you're probably our closest link to the HTML group: could you explain the rationale behind this? 
--
Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma Goldman
Received on Thursday, 9 September 2010 19:30:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:39 GMT