- From: Cameron McCormack <cam@mcc.id.au>
- Date: Wed, 7 Feb 2007 08:58:24 +1100
- To: public-appformats@w3.org
Hi.
This is a last call comment from the SVG WG on the XBL 2 Editor’s Draft
(dated 23 January 2007).
With respect to authors implementing the standard SVG interfaces in a
binding[1], we’ve found that it is not possible to have an
implementation of particular interfaces (such as SVGElement and
SVGLocatable) because bindings cannot traverse the flattened tree from
the xbl:template element to the bound element. This functionality was
available in sXBL (the xblParentNode property of the NodeXBL interface).
For example, the SVGElement interface has a property
ownerSVGElement, which simply returns the closest ancestor svg element.
In this document:
<svg xmlns="http://www.w3.org/2000/svg">
<xbl xmlns="http://www.w3.org/ns/xbl">
<binding element="ex|container">
<template>
<content/>
</template>
</binding>
<binding element="ex|something">
<implementation>
({
get ownerSVGElement() {
// XXX what here?
}
})
</implementation>
</binding>
</xbl>
<ex:container>
<ex:something/>
</ex:container>
</svg>
there is no way for the ownerSVGElement getter to traverse up the
flattened tree to find the svg element to return.
The SVG WG requests that a feature that allows script to traverse up the
flattened tree be added.
Thanks,
Cameron
-for the SVG WG
[1] http://lists.w3.org/Archives/Public/public-appformats/2007Feb/0018.html
--
Cameron McCormack, http://mcc.id.au/
xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
Received on Tuesday, 6 February 2007 21:58:30 UTC