Re: [Xsltforms-support] properties.doc.documentElement is null

[Chris G. <cga...@gm...>]

I know it's in poor taste to post a reply to one's own post, but I'm
currently stuck and desperate. That's a bad combination. :)

Doing a comparison on the transformed XForms form, I notice that the escaped
<tags> are re-escaped on the second form in the generated Javascript. i.e.

<xforms:input> becomes '&lt;xforms:input&gt;' in the first form.
&lt;xforms:input&gt; becomes '&amp;lt;xforms:input&amp;gt;' in the second
form.
and I suspect (although it all crashes, so I can't get a good read to tell
for sure) that on the third form it would become
'&amp;amp;lt;xforms:input&amp;amp;gt;'

Now there is an escapeEntities.xsl.xml component that I /think/ was designed
to mitigate this problem. Is that perhaps malfunctioning on iterative calls
to the XForms form?





On Mon, May 24, 2010 at 4:24 PM, Chris Gamache <cga...@gm...> wrote:

> This happens on the third post.
>
> XSLTForms Exception
> --------------------------
>
> Error initializing :
>
> ("status")@http://path/to/xsltforms/xsltforms.js:640
> ()@http://path/to/xsltforms/xsltforms.js:1071
> initImpl()@http://path/to/breakfast.xml:30
> init()@http://path/to/breakfast.xml:36
> onload([object Event])@http://path/to/breakfast.xml:1
>
>
> TypeError
>
> properties.doc.documentElement is null
>
>
>
>
>
>
> The served XML will render when it is not generated as a result of another
> XForms form.
>
> I'm using revision 403. Any ideas?
>