[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Re: Repost: IE applies transformation, Fx does not

Subject: Re: Re: Repost: IE applies transformation, Fx does not
From: "M. David Peterson" <m.david@xxxxxxxxxx>
Date: Tue, 04 Apr 2006 07:47:42 -0600
Re:  Re: Repost: IE applies transformation
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="http://www.w3.org/1999/xhtml">
...
</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 the
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

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.