Re: XSLT and DTD
| Newsgroups | gmane.comp.mozilla.devel.layout.xslt |
|---|---|
| Organization | http://groups.google.com |
| Message-ID | <[email protected]> |
On Apr 11, 1:01 pm, "Michael Vincent van Rantwijk, MultiZilla" <[email protected]> wrote: > Martin Honnen wrote: > > Michael Vincent van Rantwijk, MultiZilla wrote: > > >> Are you sure that your script is loaded and run when it fails to > >> transform? > > > DOM inspector shows that the new nodes have been inserted into the > > document but somehow the display is not being updated with Firefox 2.0. > > Interesting, I had a similar (still unsolved) problem with SeaMonkey > v1.1.1 and this test case also fails in SeaMonkey v1.1.1 (sharing source > code). > > Michael The URLs http://arsmc.org/documents/canobie_series.xml and http://arsmc.org/documents/canobie_series.html would in Firefox and SeaMonkey but not Netscape. Note: Both of these use the same javascript involving xmlhttprequest and xsltprocessor using the document.url as a parameter to the XSLT. The new page "completely replaces" the old page after XSLT transformation rather than merely effecting the body. My guess is this is due to Netscape working in XHTML mode while Firefox and SeaMonkey are in quirk mode but this is merely an educated guess based on what I think the Dom Inspectors for each are telling me. Note: These 2 urls render in Opera 9 and Adobe Scout using the same javascript path. IE works but of course uses a completely different method of supporting the transformation and rendering. As I have stated in previous posts if I force Firefox into xhtml mode using a DTD it fails to render in both instances. John Perkins