Comments on: Cross-Browser XML and XSLT Processing

By: Ryan Morr

Ryan Morr — Sat, 07 Mar 2009 21:00:50 +0000

@Sasha Firsov One solution I am aware of is performing an XPath query for xsl:import and xsl:include nodes and then reloading them in Javascript. If your looking for a better place to post such a question you can try one of these google groups; comp.lang.javascript or comp.text.xml.

By: Sasha Firsov

Sasha Firsov — Thu, 05 Mar 2009 20:50:18 +0000

Hey, Ryan & mundi
I was able to make the whole stack of pipeline client transformation. Works everywhere. Even on current Chrome on file system. Safari and Chrome on web unfortunately not allowing the xsl:include. Since there is a solution which work from file system, the WebKit resistance most likely comes from security . Any idea how to fight it? And where to post such question?

By: Ryan Morr

Ryan Morr — Mon, 09 Feb 2009 00:09:02 +0000

@mundi

I may add support for those features at some later point in time, for now I wanted to keep it simple for the basic functions.

Both Sarissa and jQuery transform are good resources, my only concern is the use of browser detection. I can never in good faith rely on something like that.

By: mundi

mundi — Sun, 08 Feb 2009 15:31:28 +0000

good article. i would also add the ability to set parameters in the stylesheet. this is key for doing things like sorting/filtering. also, in my experience, getting xsl:import and xsl:include to work cross browser is also a tough nut to crack. (webkit)

sarissa is the best i’ve seen so far
jquerytransform looks good too