W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2013

Re: [whatwg] URL resolution of fragment urls in html5 webapps

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 11 Sep 2013 11:53:35 +0100
Message-ID: <CADnb78iS2LsMporp8qKxFmmBy-rHH7q++_-osP94oaWAtjzdcw@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Jake Archibald <jakearchibald@google.com>, Jeni Tennison <jeni@jenitennison.com>, Rafael Weinstein <rafaelw@google.com>, whatwg <whatwg@whatwg.org>, Alex Russell <slightlyoff@google.com>, Igor Minar <iminar@google.com>
On Tue, Sep 10, 2013 at 8:34 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Wed, 10 Jul 2013, Rafael Weinstein wrote:
>> I'm curious: Is it useful to have fragment URL resolve against anything
>> other than the "display" url? I.e. when is the current behavior wrt
>> fragments appropriate.
> It's a good question. I thought the old IETF specs for URLs said you had
> to do otherwise, but nobody seems to have implemented that.

Browsers have been inconsistent on this actually, not sure if they
still are. I think if we want to do this differently, then after
trimming whitespace to obtain the URL, the <a> element should have a
special case for # and pick a different base URL at that point.

https://tools.ietf.org/html/rfc2396#section-4.2 has the vague wording
that does not take the base URL into account. In
https://tools.ietf.org/html/rfc3986#section-4.4 it does. The problem
with the former is that it's not clear when it applies, but we could
make that clear by only doing it in certain contexts, as I suggested

Received on Wednesday, 11 September 2013 10:54:02 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:09 UTC