XSL(T) errors should be more verbose

Assigned to



13 years ago
9 years ago


(Reporter: Philip Withnall (unavailable), Assigned: peterv)


Windows XP

Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041221 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041221 Firefox/1.0+

When Gecko encounters an error in an XSL(T) stylesheet for an XML file, it
should give a more verbose and informative error message (as it does if it finds
an error in an XML file) instead of just saying that the was an error.

Reproducible: Always

Steps to Reproduce:
1. Create a perfect XML document, and in it, reference an imperfect XSL(T)
2. View the XML document in Firefox/Mozilla
3. Spend hours trying to work out what's wrong with your XSL(T)

Actual Results:  
I spent ages trying to find out what was wrong with my XSL(T)

Expected Results:  
I should be able to pinpoint the error easily courtesy of a verbose error message
Assignee: validation → peterv
Component: DOM: Validation → XSLT
QA Contact: keith
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

13 years ago
This is the behaviour in Firefox 1.0.7 :-P


13 years ago
Ever confirmed: true

Comment 3

12 years ago
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060214 Firefox/1.6a1
This is still happening in the latest build.

Compare a typical XML error message:
XML Parsing Error: mismatched tag. Expected: </xsl:stylesheet>.
Location: file:///var/www/Example-pages/Syn-JS/syn-js.xsl
Line Number 24, Column 4:

With a typical XSLT error message:
Error during XSLT transformation: (null)

Comment 4

11 years ago
*** Bug 316319 has been marked as a duplicate of this bug. ***

Comment 5

11 years ago
I agree. All I get from is "Error during XSLT transformation: An unknown XPath extension function was called." which isn't a lot of help!

Comment 6

11 years ago
Agreed.  XSLT debugging if Firefox is not easy.
QA Contact: keith → xslt
You need to log in before you can comment on or make changes to this bug.