275825 - Essential node navigation in XSLT fails

Status: RESOLVED DUPLICATE of bug 275824

(Firefox :: General, defect)

Description

[mitchgould]

Although many examples from "XSLT Quickly" by Bob Ducharme succeed in Mozilla,
some others fail without an error message, resulting in a gray client window.
This includes important node-navigation tasks in XSLT (attached).

/////////////////////////////////////

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     version="1.0">
<xsl:output method="xml" omit-xml-declaration="yes" indent="no"/>
<?startSampleFile ?>

<!-- xq103.xsl applies style to xq102.xml -->
<!-- Fails in Firefox: client area just becomes a gray window -->
<!-- Works fine in IE6 -->
<!-- Excellent demo of node navigation in XSLT -->
<!-- XSLT Quickly by Bob Ducharme -->

<xsl:template match="item[3]">
~~~~ Start of item element's template ~~~~
1. This node: {<xsl:apply-templates/>}
2. First node: {<xsl:value-of select="../item[1]"/>}
3. Last node: {<xsl:value-of select="../item[last()]"/>}
4. Preceding node: 
   {<xsl:value-of select="preceding-sibling::item[1]"/>}
5. Next node: {<xsl:value-of select="following-sibling::item[1]"/>}
6. flavor attribute value of first node: 
   {<xsl:value-of select="../item[1]/@flavor"/>}
~~~~ End of item element's template ~~~~
</xsl:template>

<?endSampleFile ?>

<!-- Dont bother with the other ones. -->
<xsl:template match="item"/>

</xsl:stylesheet>

/////////////////////////////////////////////////

<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="xq103.xsl"?>

<!-- xq102.xml - style it using xq103.xsl -->
<!-- Fails in Firefox: client area just becomes a gray window -->
<!-- Works fine in IE6 -->
<!-- Excellent demo of node navigation in XSLT -->
<!-- XSLT Quickly by Bob Ducharme -->
<list>
<item flavor="mint">First node.</item>
<item flavor="chocolate">Second node.</item>
<item flavor="vanilla">Third node.</item>
<item flavor="strawberry">Fourth node.</item>
</list>

Comment 1

[Phil Ringnalda (:philor)]

*** This bug has been marked as a duplicate of 275824 ***