https://www.w3.org/Bugs/Public/show_bug.cgi?id=29763 --- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> --- The use case seems viable, indeed. But there was a reason that xsl:param was made implicitly public (to enforce it is always settable externally). Now by overriding it with xsl:variable it can be hidden. I'm unsure whether we have properly understood the consequences of this. Maybe there's no problem and it should / could stay the way it is. I'll chew a bit more on this. -- You are receiving this mail because: You are the QA Contact for the bug.Received on Monday, 1 August 2016 09:11:29 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC