- From: <bugzilla@jessica.w3.org>
- Date: Mon, 19 Oct 2015 12:26:55 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29210
Abel Braaksma <abel.braaksma@xs4all.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abel.braaksma@xs4all.nl
--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I think this error is not needed in the first place, so I would like to
consider dropping the error entirely (your A2 above). Though I am not sure it
should apply the imports from the used package, since it is used in the using
package in xsl:override, it seems to make sense to have xsl:apply-imports apply
to the imports scoped to the using package.
This is somewhat similar to, say, a named xsl:output, which can only be
referenced from within the using package (in case of xsl:override), but you can
never access the named outputs from the used package. It seems odd if use a
different rule for xsl:apply-imports (apart from the fact that, if the package
is compiled, its imports may not be available anymore).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 19 October 2015 12:26:58 UTC