Bug 11782 - XSL transform ignores disable-output-escaping
Summary: XSL transform ignores disable-output-escaping
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: XML (show other bugs)
Version: 419.x
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-08 10:00 PST by Brian Bockelman
Modified: 2008-03-02 03:46 PST (History)
1 user (show)

See Also:


Attachments
a test that works (773 bytes, text/html)
2007-07-05 04:29 PDT, Alexey Proskuryakov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Bockelman 2006-12-08 10:00:02 PST
When transforming XML with an XSL stylesheet, you should be able to disable output escaping when desired.

For example, I should be able to do the following:

<img>
  <xsl:attribute name="src">/graphs?var=value<xsl:text disable-output-escaping="yes">&amp;</xsl:text></xsl:attribute>
</img>

the "src" attribute of "img" should be "/graphs?var=value&".  In Safari (but not FF or IE6), you end up with "/graphs?var=value&#38;".

The reference for this in the XSLT spec is here:

http://www.w3.org/TR/xslt#disable-output-escaping
Comment 1 Alexey Proskuryakov 2007-07-05 04:29:52 PDT
Created attachment 15399 [details]
a test that works

I have tried to make a test case for this bug, but couldn't get the attribute value to be escaped, even when I removed disable-output-escaping. I'm getting identical results from Firefox 2, r18068 (from December 8th) and r23922.

Please provide more information about this issue.
Comment 2 Robert Blaut 2008-03-02 03:46:32 PST
(In reply to comment #1)
> Created an attachment (id=15399) [edit]
> a test that works
> 
> I have tried to make a test case for this bug, but couldn't get the attribute
> value to be escaped, even when I removed disable-output-escaping. I'm getting
> identical results from Firefox 2, r18068 (from December 8th) and r23922.
> 
> Please provide more information about this issue.
> 

I also cannot confirm the bug. No more info form reporter on this subject since initial reporting. Marked as WORKSFORME.