Re: [xsl] Re: Repost: IE applies transformation, Fx does not

Subject: Re: [xsl] Re: Repost: IE applies transformation, Fx does not
From: "Manfred Staudinger" <manfred.staudinger@xxxxxxxxx>
Date: Tue, 4 Apr 2006 08:30:42 -0700
Hi David,

I've already resolved my problem - but still my broader picture is
First, what are _all_ the methods to load a xml file dynamically, separated
in two classes
a) those which trigger a xslt transformation (e.g. location.replace)
b) those which don't (e.g. XMLHTTPrequest)

Second, is there any method which belongs to both classes, IOW's
someone which triggers the xslt transform, or ignores the PI
(depending on a parameter, a switch, or whatever) ?

Regards, Manfred

On 04/04/06, M. David Peterson <m.david@xxxxxxxxxx> wrote:
> Hi Manfred,
> I assume you are using location.replace("uri_of_file_to_replace") such
> that you can push the new document into the position of the current
> document, resulting in the current uri/related-document being popped off
> the stack and, in essence, forgotten about.  If yes, is there a specific
> reason for doing this e.g. transaction flow that, if the back button
> were clicked, would negate the entire transaction?  If no, there are
> several other way's to accomplish the desired task, such as simply
> setting the value of document.location to the desired URI of the new
> document.  Of course, if this is designed to gain the benefit of
> replacing the first postion of ~history.back(), and this functionality
> is crucial to your application functioning properly, then let me know
> and I will dig a littler deeper into the various specs to determine if
> the behavior of Moz/Fx allows for the making assumptions as to what
> content can be expected, and what, if anything, can be "overlooked"
> (such as PI's in an XML document).
> BTW.. what is document type of the problem xml file being served as?
> Manfred Staudinger wrote:
> >The difference stems from the fact, that instead of XMLHTTPrequest, I'm
> >using the location.replace method for retrieving the xml in IE (to
> >avoid activX).
> >This method triggers (unexpected by me) a XSLT transformation, if the xml
> >contains a PI for the stylsheet (in _all_ xslt enabled browsers).
> >
> >Regards, Manfred
> >
> >On 29/03/06, Manfred Staudinger <manfred.staudinger@xxxxxxxxx> wrote:
> >
> >
> >>Hi list,
> >>I've a xml file with a PI specified:
> >><?xml version="1.0" encoding="UTF-8"?>
> >><?xml-stylesheet href="../view_names.xsl" type="text/xsl"?>
> >><doc xmlns="";>
> >>...
> >></doc>
> >>When I invoke a file like this with the browser, the file is fetched,
> >>gets transformed
> >>and the result is displayed, for both Fx 1.5 and IE 6.0 (MSXML 3).
> >>When I fetch the same file via javascript httprequest, then IE applies
> >>transformation automatically before giving me access to the result-tree,
> >>whereas Fx (also Opera 9.0 beta) gives me the xml input-tree.
> >>
> >>Is this difference documented anywhere?
> >>May I prevent that transformation on IE somehow?
> >>
> >>Regards, Manfred

Current Thread