- From: <bugzilla@jessica.w3.org>
- Date: Wed, 12 Feb 2014 08:51:01 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24524 C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |cmsmcq@blackmesatech.com --- Comment #1 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> --- We discussed this in Prague. The on-completion expression has no focus, so it cannot refer to the context -- unless it is lexically within a for-each-group and refers to the current group and/or the current group key. It would be easy enough to specify that references to the current group (and key?) should be impossible within on-completion, just as we do for references to the context item. Note that clause 1.c appears both here and in for-each. It seemed that it might possibly be unnecessary, but on consideration we decided to keep it for generality (i.e. 'just in case'). (Also, if we omitted it, the analysis would never hit xsl:break.) We do need to cover on-completion in rule 2 -- also parameters. In 2.b, the operands do need to be identified (and the number corrected). Should this use the GSR instead of having its own rules? On-completion requires special rules; perhaps a rule of the form "If there is an on-completion, then ... otherwise the GSR applies". -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 12 February 2014 08:51:02 UTC