RE: JS not executed AFTER transformNode

I dislike it because it removes control from me, the processor then has
particular rules it follows for how it outputs the html, in some cases it is
useful or even necessary, but those are extremely rare (can't think of any now,
just remember that I HAD to do it once, and that had could be the fault of not
being adequate at solving the problem at that time), I produce well-formed html,
I don't necessarily try to follow the xhtml spec, by well formed I mean html
that could be read in by an xml parser somewhere down the line and still be
understood as xml. 

Quoting Daniel Joshua <daniel.joshua@xxxxxxxxxxxx>:

> > if you don't want to set your output to be html (which is
> > something I hate doing personally)
> 
> So you set your output to "xml", and do your try to produce
> XHTML or just plain HTML?
> 
> I notice some people avoid setting output to "html" even when
> they want to produce HTML. Why is that? Is there a reason to
> avoid setting the output to "html" because of a bug(?) in XSL?
> 
> 
> Regards,
> Daniel
> 
> 
> -----Original Message-----
> From: bry@xxxxxxxxxx [mailto:bry@xxxxxxxxxx]
> Sent: Thursday, 05 August, 2004 4:44 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  JS not executed AFTER transformNode
> 
> 
> depending on the browser and your output settings you might have a
> situation
> where you are outputting <script src="myscript.js"/> which is a problem, if
> you
> don't want to set your output to be html (which is something I hate doing
> personally) i would do the following in your script generation:
> 
> <script src="myscript.js"><xsl:text> </xsl:text></script>
> 
> there could be other problems of course, but this is a likely thing to stem
> from
> a transform.
> 
> Quoting Frederic Tsolakidis <ftsolakidis@xxxxxxxxx>:
> 
> > hi,
> >
> > I have an XSL file that I use to transform several XML
> > pages into HMTL, in the XSL file, I'm referring to
> > external javascripts, and everything works fine when I
> > browse my pages.
> >
> > For reasons too long to explain here, I've been
> > working on "simulating" xpointer's behavior thanks to
> > XMLDOM (I'm actually using sarissa) and perform my a
> > transformation in javascript.
> >
> > My JS transformation works fine, and I'm displaying
> > the result with a document.write() call.. and
> > everything seems ok, except for my included JS files,
> > which don't get processed at all (I'm using the same
> > XSL for common pages, and for pages transformed by
> > JS).
> >
> > As long as my resulting page sticks to static HTML,
> > everything is ok, but once I make it dynamic (with
> > internal or external JS) it doesn't work...
> >
> > Any idea anyone ?