W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2015

[Bug 29095] New: [xslt 3.0] Edge case inconsistency between xsl:expose and xsl:accept

From: <bugzilla@jessica.w3.org>
Date: Fri, 28 Aug 2015 11:53:46 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29095-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29095

            Bug ID: 29095
           Summary: [xslt 3.0] Edge case inconsistency between xsl:expose
                    and xsl:accept
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          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: ---

For both xsl:expose and xsl:accept, we allow multiple explicit references to
the same component, e.g.

<xsl:expose component="variable" names="v1 v2" visibility="private"/>
<xsl:expose component="variable" names="v2" visibility="private"/>

and ignore all but the last.

However, a careful reading suggests that xsl:accept validates the visibility of
all the declarations, whereas xsl:expose only validates the one that is
actually used.

I think that we should validate them all, in both cases.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 28 August 2015 11:53:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:55 UTC