RESOLVED INVALID 47453
XSLT: getting unknown system property kills the transformation 
https://bugs.webkit.org/show_bug.cgi?id=47453
Summary XSLT: getting unknown system property kills the transformation
Julian Reschke
Reported 2010-10-09 09:26:08 PDT
What steps will reproduce the problem? 1. Navigate to http://greenbytes.de/tech/webdav/xslt-test.xml 2. Check transformation result, which should *not* end after "msxsl:version" What is the expected result? XSLT continues. What happens instead? Aborts. Please provide any additional information below. Attach a screenshot if possible. This appears to be a bug in libxslt.
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2010-10-09 13:38:11 PDT
Yes, this reproduces with xsltproc on command line. Would you be willing to file a bug via <https://bugzilla.gnome.org/enter_bug.cgi?product=libxslt>?
Julian Reschke
Comment 2 2010-10-10 01:17:45 PDT
(In reply to comment #1) > Yes, this reproduces with xsltproc on command line. Would you be willing to file a bug via <https://bugzilla.gnome.org/enter_bug.cgi?product=libxslt>? Done: https://bugzilla.gnome.org/show_bug.cgi?id=631803
Julian Reschke
Comment 3 2011-05-10 01:19:06 PDT
Wow. 6 months with no progress on a bug that causes a program abort.
Alexey Proskuryakov
Comment 4 2011-05-10 08:55:25 PDT
What action do you expect from us, short of writing a new XSLT processor to replace libxslt?
Julian Reschke
Comment 5 2011-05-10 09:02:37 PDT
Help getting libxslt fixed, for instance? Just because a "third-party" library is used doesn't mean it's entirely somebody else's problem, right?
Julian Reschke
Comment 6 2011-07-20 07:32:08 PDT
Still present in Safari 5.1.
Julian Reschke
Comment 7 2012-08-21 07:48:37 PDT
(In reply to comment #4) > What action do you expect from us, short of writing a new XSLT processor to replace libxslt? Note that libxslt has been fixed in the meantime.
Alexey Proskuryakov
Comment 8 2012-08-21 09:31:16 PDT
Marking INVALID as a non-WebKit issue.
Note You need to log in before you can comment on or make changes to this bug.