You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/10/05 21:01:02 UTC

DO NOT REPLY [Bug 1604] - Scriptable HTML attributes need to be returned unescaped

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1604>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1604

Scriptable HTML attributes need to be returned unescaped

keshlam@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement



------- Additional Comments From keshlam@us.ibm.com  2001-10-05 12:01 -------
The escaping rules are defined very specifically, and we have to follow them for 
compatability with other XSLT processors 
(see http://www.w3.org/TR/xslt#section-HTML-Output-Method for the details). 

As far as I can tell, there is no special provision there for scriptable 
attributes, though there is for scriptable elements and for attributes 
containing URIs.

I don't think that leaves us with a lot of choice in this matter, at least in 
normal operation. If we wanted to create a subclass of the serializer which 
provided this functionality, and make it a custom feature of Xalan (<xsl:output 
mode="xalan_smarter_html"/> or something like that), that might be possible.

So unless I've misssed something, I think we have to knock this down to 
Enhancement