W3C home > Mailing lists > Public > public-html@w3.org > February 2013

Re: Bug 12543 and URL parsing in general

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sun, 17 Feb 2013 19:02:20 +1100
Message-ID: <CAHp8n2namT=DLte0jXPYO9787fA-S1N6TDXQR_MNtcauL0F5=w@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Travis Leithead <travis.leithead@microsoft.com>, Erika Doyle Navara <Erika.Doyle@microsoft.com>, "public-html@w3.org" <public-html@w3.org>
Please note that I am about to cherry-pick the following commit from the

It is making use of the new URL spec.

It would be good to analyse what open issues around URL remain after this
and continue trying to resolve them.


On Thu, Feb 7, 2013 at 4:35 AM, Julian Reschke <julian.reschke@gmx.de>wrote:

> On 2013-02-06 18:20, Travis Leithead wrote:
>> From: Julian Reschke [mailto:julian.reschke@gmx.de]
>>> On 2013-02-05 23:36, Erika Doyle Navara wrote:
>>>> Bug 12543 [1] requests that step 12 (replacing "\" with "/") of the
>>>> "resolve a URL" algorithm be removed, as Gecko behavior has shown that
>>>> it isn't needed for compatibility. The discussion in a related bug 14693
>>>> [2] also highlights other problems with step 12 and the algorithm in
>>>> general. It has been suggested that the entire section of URL parsing be
>>>> removed and instead defer to the URL spec [3].
>>>> Are there any objections to this course of action? If not, I'll take a
>>>> stab at removing the relevant sections and stage them in a branch before
>>>> committing to HTML5.1 and resolving 12543 as fixed.
>>>> ...
>>> Deferring to another spec that has the same problem doesn't resolve the
>>> issue; it just moves it elsewhere.
>> While conceptually correct, it does matter to the HTML5 editors :)
>> In any case, it seems as if there was a rough proposal to keep the "\"
>> handling since it is implemented in all but Gecko browsers. To this end,
>> the URL parsing spec does include it.
>> Julian, in my reading between the lines, are you proposing we should
>> remove the "\" handling from both HTML5 and the URL spec?
> Well, we shouldn't pretend that by referring to the "URL" spec any of
> URL-related problems gets solved :-)-
> Best regards, Julian
Received on Sunday, 17 February 2013 08:03:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 17 February 2013 08:03:10 GMT