- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 May 2015 16:34:00 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24040
Abel Braaksma <abel.braaksma@xs4all.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |abel.braaksma@xs4all.nl
Assignee|abel.online@xs4all.nl |mike@saxonica.com
--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
My take on this:
> result-document-1107
You can only find the sort key specification by evaluating the
xsl:call-template, which contains the xsl:result-document. Only after this
evaluation you find that the sort key is redundant and can be ignored, but by
this time you have already evaluated it.
I think that in this case the error cannot be side-stepped.
> result-document-1109
This is different. The param is not used, so the error is never raised (unless
a processor detects the error statically). So yes, here I believe it can be
side-stepped.
> result-document-1110
Same here, param is never used, no need to throw the error.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 15 May 2015 16:34:02 UTC