Kurt Cagle:
> Not completely sure about that. I do agree that it would probably be
> fairly inefficient, but I'm not sure that a Javascript shadow tree
> arrangement would be out of the realm of possibility. Been thinking
> about implementing something like that for IE anyway, so I can start
> developing cross platform bindings without getting locked in JS
> spaghetti code.

I don't think it would be that inefficient, but there'd be the issue of
having things like:

<svg ...>
<g id="stuff">
<ex:star cx="100" cy="100" numpoints="5" r="100" r2="50"/>
<g>
<!-- This is the shadow tree for the previous ex:star element -->
<path d="..."/>
</g>
</g>
<script>
for (var n = document.getElementById("stuff"); n;
n = n.nextSibling) {
if (n.nodeType == Node.ELEMENT_NODE) {
// do something with every element child of "stuff"
}
}
</script>
</svg>

where you might trip over the 'g' element that is effectively the shadow
tree of the ex:star element.

--
Cameron McCormack ICQ: 26955922
cam (at) mcc.id.au MSN: cam (at) mcc.id.au
http://mcc.id.au/ JBR: heycam (at) jabber.org