On 11/5/06, Cameron McCormack <[EMAIL PROTECTED]> wrote:
Ah right, I remember now: it's because the prefix is resolved inside the
shadow tree, and the namespace lookup code doesn't cross the "boundary"
from the shadow tree to the actual document.
That makes sense.
You can get around this by declaring the
namespace again on some element inside the shdaow tree (e.g. the
xbl:content or text element).
I tried this on the text element inside the second xbl:template. Here
is what that whole shadow tree definition looks like now:
<text xmlns:myNS="http://example.com";>
<xbl:content includes="myNS:label" />
</text>
Unfortunately, while the error has gone away, it's once again silently
failing to render the text. I've tried poking the XPath statement a
little, to no success.
--
Jason McIntosh
President and Founder
Volity Games
[EMAIL PROTECTED]
617-792-3829
Digital Games for Analog People.
http://volity.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
