| Summary: | WebKit's XSLTProcessor implementation does not throw exceptions | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | XML | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | ahmad.saleem792, ap, arthur_webkit, batmanisback987, bfulgham, cdumez, ian, isc888x, matt.pslab, philip, rniwa, samwhiteman, sourabh.editsoft |
| Priority: | P4 | ||
| Version: | 420+ | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://lxr.mozilla.org/seamonkey/source/content/xsl/public/nsIXSLTException.idl | ||
| Bug Depends on: | 3275 | ||
| Bug Blocks: | 9901 | ||
|
Description
Eric Seidel (no email)
2005-10-20 13:33:17 PDT
This only applies after: http://bugzilla.opendarwin.org/show_bug.cgi?id=3275 Is this fixed now? AFAIK, XSLTException doesn't really exist in Mozilla either (they have an IDL, but apparently never use it). In a broader sense, WebKit XSLT error reporting is even more limited than what we have for other kinds of mistakes. Chromium / Blink - https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/xml/xslt_processor.idl;l=1?q=XSLT_Processor.idl Webkit - https://github.com/WebKit/WebKit/blob/dd956d5e74249681ddf904e0bbe401f308b65e0f/Source/WebCore/xml/XSLTProcessor.idl Firefox / Gecko - https://hg.mozilla.org/mozilla-central/file/012853bd80b7/dom/webidl/XSLTProcessor.webidl ________ Is this something needed now? Thanks! Looks like Gecko still raises exceptions, and while Blink doesn't, there is a relatively fresh TODO about it. In a brief Firefox testing, I got an Exception, not an XSLTException, FWIW. |