This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The introduction text on default modes (3.8.2 The [xsl:]default-mode Attribute) contains a conflicting statement, in the introduction, the value #default is allowed, but then the text says in the second para: <quote> The value MUST either be an EQName, or the token #unnamed which refers to the unnamed mode. It is not necessary for the referenced mode to be explicitly declared in an xsl:mode declaration. </quote> In other words, the "must" in this sentence seems to remove the ability to use #default as mode name. Also, I think it will make sense to extend the above sentence with something like "[...], regardless of the setting of xsl:package/@declared-modes". In addition, I was wondering if it makes sense to allow #current, which will have the same meaning as using <xsl:apply-templates mode="#current"/> and is a shortcut for a common programming style where inside an xsl:template, one typically wants to stay within the current mode, unless you specify otherwise.
> in the introduction, the value #default is allowed My mistake, the text refers to the mode attribute of xsl:template/apply-templates: > "When the mode attribute of these elements is omitted, or when it contains > the value #default, [...]" Leaving the bug open for possible inclusion of #current here.
Today the WG discussed the inclusion of #current in @default-mode and decided not to add this feature, therefore I am resolving this bug as WORKSFORME.