Re: parsing URI (references) according to RFC 3986

On 2011-06-23 18:21, Anne van Kesteren wrote:
> On Thu, 23 Jun 2011 18:15:24 +0200, Julian Reschke
> <julian.reschke@gmx.de> wrote:
>> Yes, they are treated differently, one is a reference only consisting
>> of a path, the other one only consisting of a fragment identifier.
>>
>> Their resolution is IMHO clearly described in RFC 3986; could you be a
>> bit more specific about what your concern is?
>
> In a document /foo with a base URL http://example.org/ you have a link
> #foo (<a href="#foo">test</a>). This is considered a same-document
> reference and you will scroll down to #foo rather than go to
> http://example.org/. At least, per the latest set of RFCs. Earlier RFCs
> which Gecko followed are different (IIRC).

Ah.

So are we talking about 
<http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.5.1>? Maybe 
re-read what it says, and decide whether there's a conflict with what 
HTML5 wants/needs?

Best regards, Julian

Received on Thursday, 23 June 2011 16:26:56 UTC