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

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

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.

I'll take a look and double-check. Both IE and Chrome seem to be doing the transformation OK, though, and the Web Developer extension in Firefox is displaying html that looks valid for the generated source. How accurate is the generated source window?

Does it show the exact source used to render? – Bill Michell Oct 24 '08 at 7:09 If you generalise your answer, I'll be happy to accept it. I can't accept my own answer... – Bill Michell Oct 24 '08 at 9:58 Also, do not use underscore in the name of the XSLT file.

I had this, and when I changed to a filename without underscore, it worked fine in Firefox. – Amigable Clark Kant Aug 24 '10 at 23:47.

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.

– ddaa Oct 24 '08 at 8:49 1 No. I had an xpath problem. String-length() on IE and Chrome doesn't mind if the argument is a node list, but XML Spy complains that there are "Too many items" and changing the expression made Firefox spring back to life.

– Bill Michell Oct 24 '08 at 8:56 Is there a way to get an error message from firefox? I have the same problem and XML Spy does not complain.8-/ – hstoerr Aug 30 '10 at 13:06.

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.).

Try serving it as application/xml instead of text/xml.

That doesn't help. – Bill Michell Oct 22 '08 at 8:44 Sometimes it does for other browsers, so not a bad guess. – Amigable Clark Kant Oct 14 '10 at 20:18.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.