On Wed, Sep 26, 2007 at 08:09:06PM +0300, Ivan Kurmanov wrote: > Hi friends, > > When building a result tree fragment in a stylesheet, I use > xsl:attribute to create/set value of an attribute. If I first copy > an attribute from the source tree fragment and then I > override its value with an xsl:attribute. As I understand, > this is absolutely valid behavior, according to the xslt 1.0 > specification. [1] > > But I have a feeling that a few versions ago libxslt would > instead give precedence to the original attribute value; the > attribute which appears first in an element would set the > value, the following attributes with the same name would > be ignored. And some of my older stylesheets seem to > support this hypothesis by actually relying on this behavior. > > Was it really the case some time ago in libxslt? > > I've looked at the history of changes at the News page [2], > and didn't find anything like that mentioned. This is more of > a sanity checking type of question.
A long time ago there was an issue similar to this but I think this has been fixed for at least a couple of years. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ [email protected] http://mail.gnome.org/mailman/listinfo/xslt
