Re: [xsl] IE Client side transformation issue

Subject: Re: [xsl] IE Client side transformation issue
From: "Ilya Sterin" <sterini@xxxxxxxxx>
Date: Thu, 2 Aug 2007 19:45:09 -0400
Everyone, thanks for the responses, they all helped.  Andrew, you're
correct, after inspecting the html output, evidently IE is not as
forgiving as FF when it comes to certain ridiculous details.  We were
using template divs which were self closing divs as well as self
closing textarea inputs.  This is not supported by IE when not using
xhtml doctype I guess.  The xhtml doctype breaks various things in FF.
 The processor also changed empty div tags to self closing div tags
and did the same with any other element, so we had to insert a
non-breaking space in divs and textarea elements. IE stops parsing
when it gets to an erroneous element (well, one it considers
erroneous) and though that element is of course not available as a
part of the rendered DOM.

Thanks again to everyone.


On 7/29/07, Andrew Welch <andrew.j.welch@xxxxxxxxx> wrote:
> On 7/29/07, Ilya Sterin <sterini@xxxxxxxxx> wrote:
> > We have an application that does client side transformation.  All
> > works fine in FF and the transformation itself seems to work fine in
> > IE.  The problem that we're having is with the onload handler.  Seems
> > like although the transformation succeeds, the DOM is not available,
> > though the javascript onload handler is executed, but any
> > document.getElementById fail.  I can search for any div or other
> > element by id and the return is always null, though when looking at
> > the source of the transformation, the div element with that ID exists.
> >  Again, this works fine in FF, so it seems like IE is behaving
> > differently in regards to DOM lifecycle/availability after the
> > transformation succeeds.
> The first thing to do is make sure result HTML works independently of
> the transformation process.
> Do you experience the same problem if you just load the HTML in IE
> without doing the transform?  If so, fix it and work backwards.
> If not, try and produce a small working example showing what the problem is.
> cheers
> andrew
> --

Current Thread