Bug 89279 - xslt forwards compatible mode does not work
Summary: xslt forwards compatible mode does not work
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://greenbytes.de/tech/tc/xslt/#ft...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-16 02:21 PDT by Julian Reschke
Modified: 2012-10-10 08:36 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Reschke 2012-06-16 02:21:21 PDT
The stylesheet below:


<?xml version="1.0" encoding="UTF-8"?>
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:test="#tes
t"
               xmlns:tc="mailto:julian.reschke@greenbytes.de?subject=xslt"
               version="2.0">
   <xsl:output method="html" encoding="iso-8859-1" version="4.0"
               doctype-public="-//W3C//DTD HTML 4.01//EN"
               indent="no"/>

   <xsl:template match="/">
      <html>
         <head>
            <title>xsl:function</title>
         </head>
         <body>
            <xsl:choose>
               <xsl:when test="function-available('test:test')">
                  <p>
            Result: <xsl:value-of select="test:test()"/>
                  </p>
               </xsl:when>
               <xsl:otherwise>
                  <p>
                     <tt>xsl:function</tt> not supported, but properly handled
(ignored)</p>
               </xsl:otherwise>
            </xsl:choose>
         </body>
      </html>
   </xsl:template>

   <xsl:function name="test:test">YES</xsl:function>

</xsl:transform>

should either result in "YES", or in "xsl:function not supported, but properly
handled (ignored)". Instead, it aborts with:

compilation error: file ... line 30 element function

(see also https://bugzilla.gnome.org/show_bug.cgi?id=677901)
Comment 1 Julian Reschke 2012-10-10 00:34:57 PDT
Note that this libxslt bug has been fixed 2 months ago.
Comment 2 Alexey Proskuryakov 2012-10-10 08:36:21 PDT
Thank you for the update, marking INVALID as a non-WebKit issue.