Hi,

Well, yes for the initial transformation of the xml data, xml 3 would be 
used, then there are further transformations kicked off by events on the 
client side.

I don't think the problem is really xsl related, but before I tried to use 
<xsl:apply-imports> to seperate some of the code, the javascript didn't throw 
an error.

Now I get an error 'null is null or not an object' in the procedure that is 
executed duing BODY onload

So I think that the complete DOM has not finished loading into IE, but theat 
procedure runs anyway, and cannot find the object it is trying to change.

Is there some way to check if the xsl transformation is complete (including 
all imported sheets) and the DOM is complete before I run any more javascript 
code?

Thanks for your help, I know I am not explaing this very well, but your 
questions are forcing me to explain it better

Philip
"Martin Honnen" wrote:

> 
> 
> Philip wrote:
> 
> 
> > Yes it's javascript on the client that runs from the HTML BODY onload event.
> > 
> > The xsl transformation happens on the client I believe, as the server just 
> > sends xml with the xml-stylesheet defined.
> > 
> > We are using MSXML4.
> 
> If you send XML with <?xml-stylesheet?> to the client then IE 6 and 
> later use MSXML 3 to run the transformation. Why do you say "we are 
> using MSXML 4"?
> 
> And if the problems occur with JavaScript and the body onload event, why 
> do you think the problem is XSLT related or related to 
> <xsl:apply-imports>? Does the script run additional transformations?
> 
> 
> -- 
> 
> 	Martin Honnen --- MVP XML
> 	http://JavaScript.FAQTs.com/
>