Has anyone noticed a bug in IE5b with it's XSL methods, or is it
just me and my files? When I use

<xsl:choose>
  <xsl:when match="*[rdf:Description]">
    <xml:text>matches found: </xml:text>
    <xsl:eval>childNumber(this.lastChild)</xsl:eval>
  </xsl:when>
  <xsl:otherwise>
     <xml:text>Sorry, your search yielded no results.</xml:text>
   </xsl:otherwise>
</xsl:choose>

to output the children count of an element if there are any children, IE5b
returns

line = 1, col = 0 (line is offset from the tag) Error returned from
property or method call 

and then sometimes it seems to work. Should it work, or... what? Also with

<xsl:if match="*[dc:Language/rdf:Value]">
  <xml:text> -  
</xml:text><xsl:eval>transformLanguage(selectSingleNode("//dc:Language/rdf:Value").text)</xsl:eval>
</xsl:if>

with transformLanguage being a script in <xsl:script>, it returns the same
error from time to time - right now all the time. My mistake or not?

: jarno - kmfdm this time


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list