Cart
[Home] [By Thread] [By Date] [Recent Entries]
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).
|
