Am 20.02.2012 17:58, schrieb Invisible:
> On 20/02/2012 04:21 PM, Invisible wrote:
>
>> (I presume it goes without saying that the first thing this code snippet
>> has to do is test whether it's running on Internet Explorer or a
>> standards compliant browser. :-P Some things never change...)
>
> Oh dear God...
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=98168
>
> Short story: Using the xsl:text disable-output-escaping='yes' setting
> doesn't work. It's supposed to allow you to output arbitrary text, and
> it works with IE, but not with Firefox. And it appears they're trying to
> claim it's IE that's broken, not Firefox. >_<

Actually both are standards compliant:

"An XSLT processor will only be able to disable output escaping if it 
controls how the result tree is output. This may not always be the case. 
For example, the result tree may be used as the source tree for another 
XSLT transformation instead of being output. An XSLT processor is not 
required to support disabling output escaping. If an xsl:value-of or 
xsl:text specifies that output escaping should be disabled and the XSLT 
processor does not support this, the XSLT processor may signal an error; 
if it does not signal an error, it must recover by not disabling output 
escaping."

IE behaves as mandated for a combo of an XSLT processor and an HTML 
rendering engine.

Firefox behaves as expected (by the spec authors) for a combo of an XSLT 
processor and a DOM tree rendering engine.

The spec concludes that "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."

Post a reply to this message