- From: Arve Bersvendsen <arveb@opera.com>
- Date: Fri, 22 May 2009 21:22:19 +0200
- To: "Mark Baker" <distobj@acm.org>
- Cc: marcosc@opera.com, public-webapps <public-webapps@w3.org>
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:23:50 UTC