- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Oct 2016 09:43:56 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29940 --- Comment #1 from Michael Kay <mike@saxonica.com> --- The intent is that it should follow the same semantics as all the other mechanisms for overriding serialization parameters, e.g. * multiple xsl:output declarations with different precedence * parameter documents overriding xsl:output * xsl:result-document overriding xsl:output * API parameters overriding parameters within the stylesheet These are all designed to work the same way: - if a parameter is present then it overrides the underlying parameter, except for cdata-section-elements and suppress-indentation where it supplements it - if a parameter is absent then the underlying value is unchanged I guess it would be useful to have all these rules in one place and to be able to refer to them by name - but we can't do that for XSLT 1.0 and 2.0. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 18 October 2016 09:44:04 UTC