- From: <bugzilla@jessica.w3.org>
- Date: Mon, 13 Oct 2014 09:21:41 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27015 --- Comment #1 from Michael Kay <mike@saxonica.com> --- There's a similar problem for xsl:global-context-item. It says "If the value prohibited is specified, then the global context item must be absent." This doesn't really indicate if we expect a dynamic error in this case (and what error?), or if we expect the supplied global context item to be ignored. One could say that the decision between the two is a matter of API design and therefore out of scope. The analogy with xsl:context-item would suggest ignoring the supplied context item rather than throwing an error. This also might be appropriate given the existence of legacy APIs that supply a context item and an initial match selection in the same breath. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 13 October 2014 09:21:42 UTC