Re: XSLT and DTD

On Apr 11, 9:33 pm, "[email protected]"
<[email protected]> wrote:
> 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

I realize you most likely do not care but I also noticed the
following:

In Netscape, the urls above render sometimes and do not other times.
Making the home page contain the javascript shared by these pages
seems to make them never render in Netscape.

Note:

Once I load multiple browsers on my machine from the Firefox family
such as Flock, SeaMonkey, K-Meleon, etc I seem to have difficulty
clearing the cache.

John Perkins