5446 – WebKit's XSLTProcessor implementation does not throw exceptions

Bug 5446 - WebKit's XSLTProcessor implementation does not throw exceptions

Summary: WebKit's XSLTProcessor implementation does not throw exceptions

Status:	NEW

Alias:	None

Product:	WebKit
Classification:	Unclassified
Component:	XML (show other bugs)
Version:	420+
Hardware:	All All

Importance:	P4 Normal
Assignee:	Nobody

URL:	http://lxr.mozilla.org/seamonkey/sour...
Keywords:

Depends on:	3275
Blocks:	9901
	Show dependency tree / graph

Reported:	2005-10-20 13:33 PDT by Eric Seidel (no email)
Modified:	2022-09-02 18:50 PDT (History)
CC List:	13 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Eric Seidel (no email) 2005-10-20 13:33:17 PDT

WebKit's XSLTProcessor implementation does not throw XSLTExceptions

Comment 1 Eric Seidel (no email) 2005-10-20 13:37:20 PDT

This only applies after:
http://bugzilla.opendarwin.org/show_bug.cgi?id=3275

Comment 2 David Kilzer (:ddkilzer) 2008-02-22 16:25:16 PST

Is this fixed now?

Comment 3 Alexey Proskuryakov 2008-02-22 23:00:26 PST

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.

Comment 12 Ahmad Saleem 2022-09-02 16:19:03 PDT

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!

Comment 13 Alexey Proskuryakov 2022-09-02 18:50:35 PDT

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.