Subject: Re: [xsl] : Problems with Javascript block / Netscape From: "Michael Beddow" <mbnospam@xxxxxxxxxxx> Date: Fri, 17 Aug 2001 10:16:45 +0100 |
On Friday, August 17, 2001 9:22 AM Jeni Tennison wrote: > Chuck Evans' suggestion of putting the script in an external file and > referencing it is an even better solution if you're not generating > parts of the JavaScript on the fly. And there are two further points in favour of this approach. 1) Since an XML editor and and XSLT processor will let you accidentally damage the innards of a <script> element while editing the XSLT code, it's much better to keep the static parts out of harm's way in their own js libraries 2) You can invoke such libraries from multiple html pages. That way, they can stay cached after the first invocation and don't get sent again, even if the main page is refreshed. Michael --------------------------------------------------------- Michael Beddow http://www.mbeddow.net/ XML and the Humanities page: http://xml.lexilog.org.uk/ --------------------------------------------------------- XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] : Problems with Javascrip, Jeni Tennison | Thread | RE: [xsl] : Problems with Javascrip, Chuck Evans |
Re: [xsl] Re: Re: ?XSLT Repository?, cutlass | Date | [xsl] XSLT 2.0 reg doc, cutlass |
Month |