This was mainly an issue in Chrome, which confused us initially.
On Tue, Jul 10, 2012 at 10:11 PM, Ihe Onwuka <[email protected]>wrote:
> Thanks to some sterling persistent assistance from Steve Cameron, we
> have isolated the cause of the terrible performance of my XFORM
> (taking about 4 minutes to load).
>
> I was referencing wildcarded namespaces as in *:element in instance()
> and Xpath commands because I wanted to process elements irrespective
> of the namespace they were in (and I still would like to do that).
>
> Steve persuaded me to try the XForm by specifying the namespace (there
> is only one but I want the code to be namespace independent) and the
> load time came down to about 20 secs which is quite tolerable.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Xsltforms-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
