https://www.w3.org/Bugs/Public/show_bug.cgi?id=29574 --- Comment #18 from Max Toro <maxtoroq@gmail.com> --- Perhaps a note should be added somewhere about xsl:param. Now that public becomes private, and xsl:param is implicitly public, that means it stays public in the using package? If so the use of xsl:param should be discouraged in library packages. If I understand correctly, xsl:param can be overriden by xsl:variable and vice versa, so you can always do: <xsl:override> <xsl:param name="foo" value="$xsl:original"/> </xsl:override> ... to convert the variable of a library package into a parameter. -- You are receiving this mail because: You are the QA Contact for the bug.Received on Saturday, 30 July 2016 01:02:12 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC