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: Thu, 12 Sep 2013 16:55:04 +0100
Message-ID: <CADnb78jN9qbEdTgch_XgVjSGQ-FLFsmVVbvgFe8p27+NbU-5eQ@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: WHATWG <whatwg@lists.whatwg.org>
On Thu, Sep 12, 2013 at 4:51 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 9/12/13 5:24 AM, Anne van Kesteren wrote:
>> On Wed, Sep 11, 2013 at 7:22 PM, Ian Hickson <ian@hixie.ch> wrote:
>>> Well presumably we wouldn't want to only do it for <a>, since then links
>>> would work but SVG wouldn't (the exact opposite of the situation in
>>> Chrome now, for what it's worth).
>> Yeah, we should have to do it for everything we classify as
>> "hyperlink". <a>, <svg:a>, <area>, and <link> I suppose.
> Why only "hyperlinks", if you're doing this?

I thought it would be incompatible to do it for <form> and maybe
<iframe> and others.

> Last I checked, WebKit doesn't do it for hyperlinks, but does do it ad-hoc
> for CSS url() stuff and a few other things, depending on how it's used.

Is this for SVG thingies referenced from CSS?

Received on Thursday, 12 September 2013 15:55:33 UTC

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