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

On Thu, Sep 12, 2013 at 5:28 PM, Boris Zbarsky <> wrote:
> Or from SVG presentation attributes.  Fill, filters, masks, etc, etc, etc.
> But again, it's not clear that anything needs to be done here.  If something
> _does_ need to be done, then it needs to be done at a low level (e.g. url()
> needs to store the original string, not just the resolved url as it does now
> per CSS specs).

Currently parseURL(input, base) returns either URL or failure. We
could make it return URL, URLFragment, or failure too... Anyway, yeah,
things are possible, but it's unclear whether everyone is interested
in moving all these pieces.


Received on Thursday, 12 September 2013 16:51:37 UTC