- From: Cameron McCormack <cam@mcc.id.au>
- Date: Fri, 7 Apr 2006 12:34:05 +1000
- To: www-svg@w3.org
Hi.
As pointed out by Maciej[1], there's a potential problem with resource
documents and SVGGlobal. Consider this primary document (primary.svg):
<svg xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink" version="1.2">
<use xlink:href="resource.svg#g"/>
</svg>
and this resource document (resource.svg):
<svg xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink" version="1.2">
<g id="t"/>
<script type="application/ecmascript">
gotoLocation("somewhere.svg");
</script>
</svg>
Some questions:
* Does the resource document have a global object that implements
SVGGlobal?
* If so, will the gotoLocation method cause primary.svg or
resource.svg or to be replaced by somewhere.svg? (I think it's
unclear from the sentence "Request that the user agent traverse a
link to the given IRI." exactly what is required.)
* If the former, should the resource document be allowed to change
what document is being presented by the UA? If the latter, does
that make sense at all?
* Will the spec be changed to defer this sort of window-related
functionality to webapi's Window spec?
Somewhat unrelated:
* Why does SVGGlobal extend EventListenerInitializer2? I thought that
EventListenerInitializer2 is meant to be implemented by script
writers.
Thanks,
Cameron
[1] http://www.w3.org/mid/C5F05942-2CF1-4B75-8CF8-824AD3452B49@apple.com
--
Cameron McCormack ICQ: 26955922
cam (at) mcc.id.au MSN: cam (at) mcc.id.au
http://mcc.id.au/ JBR: heycam (at) jabber.org
Received on Friday, 7 April 2006 02:34:16 UTC