Closed
Bug 155548
Opened 23 years ago
Closed 23 years ago
parameter disable-output-escaping="yes" in <xsl:value-of ../> tag is ignored
Categories
(Core :: XSLT, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: maros.ivanco, Assigned: peterv)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020614
BuildID: 2002061408
Parameter disable-output-escaping="yes" in <xsl:value-of ../> tag is ignored.
If parameter disable-output-escaping="yes" and the input is "&#160;" mozilla
will process entity & and output "&#160;" instead of " ".
Reproducible: Always
Steps to Reproduce:
1.try files in "Additional Inforamtion" and see
2.
3.
Actual Results:  
Expected Results: (<-- there should be white space)
XSL file error.xsl:
<?xml version="1.0" encoding="ISO-8859-2" ?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" encoding="ISO-8859-2"
media-type="text/html;charset=ISO-8859-2"/>
<xsl:template match="/userDescription">
<html>
<body>
<xsl:value-of disable-output-escaping="yes" select="//userDescription"/>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
XML file error.xml:
<?xml version="1.0" encoding="ISO8859-2" ?>
<?xml-stylesheet type="text/xsl" href="error.xsl" ?>
<userDescription>Incorrect&#160;login&#160;or&#160;password&#160;specified</userDescription>
Comment 1•23 years ago
|
||
as I said before.
Mozilla mustn't do d-o-e.
What you create is a textnode  , and that's what you get.
If other processors can't encode the entity   as  , it's not our
problem.
This is what you want:
<userDescription>Incorrect login or password specified</userDescription>
and other processors should encode the nbsp as   on serializing, so that
it stays a nbsp when parsed again.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Summary: parameter disable-output-escaping="yes" in <xsl:value-of ../> tag is ignored → parameter disable-output-escaping="yes" in <xsl:value-of ../> tag is ignored
You need to log in
before you can comment on or make changes to this bug.
Description
•