165370 - [mozilla 1.1 final ] <xsl:value-of select="SUMMARY" disable-output-escaping="yes" /> (in xsl file) did not disabled the output escaping.but IE did the correct thing.

Status: RESOLVED DUPLICATE of bug 98168

(Core :: XSLT, defect)

Description

[shaohua wen]

Comment 1

[shaohua wen]

Attachment: the test case of this bug.

Please extract it and use mozilla to open the test.xml

Comment 2

[Boris Zbarsky [:bzbarsky]]

xslt

Comment 3

[Axel Hecht]

d-o-e is not intended to work. This is just not what mozilla does. 
See http://www.mozilla.org/projects/xslt/ 

Comment 4

[shaohua wen]

Please see here,I don't understand why mozilla just not allow this work.
http://www.w3.org/TR/xslt.html#disable-output-escaping

Comment 5

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

The spec says:

"An XSLT processor will only be able to disable output escaping if it controls
how the result tree is output"

Mozilla clearly doesn't control how the result tree is output since it's not
output at all. Note that what the spec calls 'output' is serialization. This is
something that mozilla doesn't do, we just build the result-tree and then show
that to the user.

The spec also says
"An XSLT processor is not required to support disabling output escaping"

and

"Since disabling output escaping may not work with all XSLT processors and can
result in XML that is not well-formed, it should be used only when there is no
alternative"

Comment 6

[shaohua wen]

OK,Can we draw this conclusion?
1.Cause Mozilla doesn't control how the result tree is output ,It is not able 
to disable output escaping .
2.An XSLT processor is not required to support disabling output escaping,so 
Mozilla will not support it.
3.Since disabling output escaping will not work in Mozilla's XSLT processor,we 
should not use d-o-e.

One more question.
Is there any way for mozilla to process the data which includes HTML tag and 
explain it as html ,but not text?

Comment 7

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Yes, you can use .innerHTML to parse html-markup. However you can't do this as
part of an XSLT transformation. So one way to do it is to store the html-markup
in your result document and then parse it using javascript and .innerHTML after
the transformation is done