- From: <bugzilla@jessica.w3.org>
- Date: Sun, 07 Jun 2015 09:30:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28774 --- Comment #3 from Tom Hillman <tomos.hillman@oup.com> --- Hi, In your counter-example, you would need to know that the text() nodes' context (section/heading/text()) - if I were interested in such a transform I would probably match on the heading element, which is why it's easy to miss this behaviour The problem is when you wish to define some over-riding behaviour for text() in general (or some other non-element node); Consider the following mode which might deliver a list of @id and @doi values as elements: <xsl:mode name="IDs" on-no-match="shallow-skip"/> <xsl:template match="@id"><ID><xsl:value-of select="."/></ID></xsl:template> <xsl:template match="@doi"><ID class="doi"><xsl:value-of select="."/></ID></xsl:template> If I understand the behaviour correctly, the templates won't match anything -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 7 June 2015 09:30:12 UTC