W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: A URL API

From: Maciej Stachowiak <mjs@apple.com>
Date: Fri, 17 Sep 2010 21:52:18 -0700
Cc: Darin Fisher <darin@chromium.org>, Julian Reschke <julian.reschke@gmx.de>, Anne van Kesteren <annevk@opera.com>, Boris Zbarsky <bzbarsky@mit.edu>, WebApps WG <public-webapps@w3.org>
Message-id: <2B912B15-A506-4EFE-B9BA-28E4915801E7@apple.com>
To: Adam Barth <w3c@adambarth.com>

On Sep 17, 2010, at 1:01 PM, Adam Barth wrote:

> On Fri, Sep 17, 2010 at 11:51 AM, Maciej Stachowiak <mjs@apple.com> wrote:
> 
>> It might be nice to provide the parts of this that make sense on HTMLAnchorElement and Location, then see if a new interface really pulls its weight.
> 
> Another piece of functionality that's missing from HTMLAnchorElement
> is the automatic stringification of URL objects.  That lets you pass
> URL objects into APIs that expect URLs represented as strings.  It's
> unlikely that we'd want to add that part of the interface to
> HTMLAnchorElement.

That does not match my recollection or testing:

http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cbody%3E%0A%3Ca%20href%3D%22http%3A%2F%2Fsome-domain.com%2Fsome%2Fpath%23frag%22%20id%3Dtest%3E%3C%2Fa%3E%0A%3Cscript%3E%0Adocument.write(document.getElementById(%22test%22))%3B%0A%3C%2Fscript%3E

Good point about the Worker use case where there is no DOM.

Regards,
Maciej
Received on Saturday, 18 September 2010 04:53:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT