W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2017

[Bug 30109] New: [xslt30] Sticky disable-output-escaping revisited

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 May 2017 14:17:53 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30109-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30109

            Bug ID: 30109
           Summary: [xslt30] Sticky disable-output-escaping revisited
           Product: XPath / XQuery / XSLT
           Version: Proposed Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Section 26.2 carries forward the following text unchanged from XSLT 2.0:

<quote>
If output escaping is disabled for an xsl:value-of or xsl:text instruction
evaluated when temporary output state is in effect, the request to disable
output escaping is ignored.
</quote>

The intent of this rule was to disallow d-o-e except for text nodes written
directly to a final result tree (i.e. text nodes that are capable of being sent
immediately to the serializer).

However, the rules on when temporary output state is set have changed, so that
this rule no longer achieves the required effect. For example, in XSLT 2.0
instructions such as xsl:attribute, xsl:comment, and xsl:processing-instruction
would set temporary output state, but in XSLT 3.0 they do not. This means that
we have unintentionally opened the door to use of d-o-e while writing
attributes or comments.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 9 May 2017 14:18:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 9 May 2017 14:18:01 UTC