- From: William Edney <bedney@technicalpursuit.com>
- Date: Fri, 22 May 2009 14:31:11 -0500
- To: "Arve Bersvendsen" <arveb@opera.com>
- Cc: "Mark Baker" <distobj@acm.org>, marcosc@opera.com, public-webapps <public-webapps@w3.org>
Arve -
Getting the value of 'src' here using
'document.images[0].getAttribute("src")' should return the relative
path.
The Microsoft guys made a big deal out of the fact that IE8 (in IE8
'strict standards' mode) will now properly return the relative path
when 'getAttribute()' is used, but the full path (as you state), when
the 'property access' version of the call is used. In IE < 8, some
extra JS to determine base path and then relativize the value would be
necessary in those browsers.
Cheers,
- Bill
On May 22, 2009, at 2:22 PM, Arve Bersvendsen wrote:
> On Fri, 22 May 2009 20:21:56 +0200, Mark Baker <distobj@acm.org>
> wrote:
>
>> I thought he had (somewhat grudgingly) accepted that way (the use of
>> relative references) forward, as IIRC, the widget: scheme idea was
>> dropped about that time. Has some new requirement emerged since then
>> that makes relative references an undesirable option?
>
> The problem here is that no user agent implementation I am aware of
> uses 'relative' URIs when resolving nodes. If you provide <img
> src="foo/bar/baz.png" /> - they all compose an absolute URI from the
> string representing the relative URI, and expose that when you query
> for the attribute value, so putting my markup fragment into a
> document at the root of http://example.com/:
>
> <html>
> <img src="foo/bar/baz.png" />
> <script>
> // The following Outputs http://example.com/foo/bar/baz.png
> alert(document.images[0].src);
> </script>
> --
> Arve Bersvendsen
>
> Opera Software ASA, http://www.opera.com/
>
Received on Friday, 22 May 2009 19:31:56 UTC