Firefox 3 doesn't apply my xslt stylesheet, but other browsers do

Question

I\'m trying to serve dynamically generated xml pages from a web server, and provide a custom, static, xslt from the same web server, that will offload the processing into th

Answer 1

I just write here for posterity - I had the same symptom, also Firefox 3. However in my case, the problem was another:

Firefox seems to really, really dislike when an XSL file has an underscore _ in the name. My XSLT file was called something like my_super_nice_xslt_which_loads_in_opera_and_ie.xsl.

So, people, let's not use underscores. Use a hyphen (minus) instead: my-super-nice-xslt-which-loads-in-opera-and-ie.xsl.

Then it will load in Firefox as well. I think I will just use dead simple names with letters and numbers in them from now on. You know the saying, "once bitten, twice shy". (In my case, I was bitten twice, but forgot the first time, so that makes me like four times shy this time.)

Answer 2

Displaying just the text elements is the behavior you would get out of an empty XSL stylesheet.

To me, that suggests that something fishy is going on with your xpath expressions, and that the xsl:template/@match attributes do not match the source document.

You do not provide enough information to diagnose further, so this blind guess is all I can offer.

EDIT: It turned out the problem was that IE and Chrome silently accept a nodeset as argument to string-length, while FF3 does not. Note that the specification mandates an optional string argument and does not specify behavior with a nodeset argument.

Answer 3

try serving it as application/xml instead of text/xml

Answer 4

If you're using NoScript, that also disables XSL stylesheets until you Allow <site>.

Answer 5

Answering my own question in the light of subsequent investigation. ddaa lead me in the right direction.

Firefox seems to be pretty fussy with xslt conversions. Double-check your xslt to ensure it has no errors that IE and Chrome are masking.

XML Spy is a good, though not cheap, product that will highlight a range of errors in the xslt. It seems to pick up at least as many issues as the Firefox renderer does.

It seems you can't rely on the Web Developer extension to pick up the problem, unfortunately.