Closed
Bug 335305
Opened 18 years ago
Closed 18 years ago
<xsl:text>'s disable-output-escaping not supported or ignored
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: boen.robot, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2 When XSLT stylesheet uses <xsl:text>, the text has a default value of disable-output-escaping set to "no". At that point, all is correct, so the output is rendered with the entities as characters. When the disable-output-escaping is set to "yes" however, firefox should transform the entities and place the actual character in the output. Examples follow... Reproducible: Always Steps to Reproduce: 1. Create and save some XSLT file that produces XHTML output and uses <xsl:text> with disable-output-escaping set to "yes". Include some entities that would form an XHTML tag, such as "<hr />". 2. Create and save some XML file which uses the created XSLT. 3. Preview the XML file in Firefox. Actual Results: The <xsl:text disable-output-escaping="yes"><hr /></xsl:text> is rendered as the text <hr /> Expected Results: Because disable-output-escaping is set to "yes", the output should have contained <hr /> which should be rendered as XHTML's horizontal rule. IE6's behaviour is right in this case. If the issue is not yet understood, just repeat the same steps in with IE and see how it renderes the <xsl:text>. Before reporting this, I saw W3C's XSLT 1.0 specification even to ensure that's the right behaviour: http://www.w3.org/TR/xslt#disable-output-escaping Note that this particular example was way too simplified and has the workaround of simply typing <hr /> without the <xsl:text>. However, more complicated stylesheets need this as it's the only way to produce a valid XHTML markup. Example: http://w3schools.invisionzone.com/index.php?showtopic=3849&view=findpost&p=19730
Comment 1•18 years ago
|
||
*** This bug has been marked as a duplicate of 98168 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•