Open Bug 204658 Opened 23 years ago Updated 1 month ago

JS XSLT interface should throw exceptions with good message and context

Categories

(Core :: XSLT, defect)

defect

Tracking

()

People

(Reporter: axel, Unassigned)

References

(Blocks 1 open bug)

Details

nsIException.message should be gotten from xslt.properties. This means that we should at least provide an nsIExceptionProvider. Context info should go into additional entries, so that js location and stack are preserved. The context info depends on the actual entry points as well. importStylesheet could throw a e.styleNode, transformToFoo could have both a nsIDOMNode e.sourceNode and a string giving a locator to a txToplevelItem as in bug 204655.
This would make handling XSLT errors much easier ;-).
Amen. We ran into this while writing XSLTProcessor in Safari. Mozilla's XSLTProcessor would fail our tests and we would have *no clue* why.
QA Contact: keith → xslt
Severity: normal → S3
Assignee: peterv → nobody
You need to log in before you can comment on or make changes to this bug.