Re: [xml] cloneNode and xml:id bug?
- From: Daniel Veillard <veillard redhat com>
- To: Bráulio Barros de Oliveira <brauliobo gmail com>
- Cc: xml gnome org, gdome gnome org
- Subject: Re: [xml] cloneNode and xml:id bug?
- Date: Wed, 17 Dec 2008 18:21:18 +0100
On Mon, Dec 15, 2008 at 04:06:29PM -0200, Bráulio Barros de Oliveira wrote:
Hello.
I'm having a problem that might be a bug of libxml (or unprobably gdome).
When I use gdome_el_cloneNode with an element that has an xml:id attribute
then the new cloned element get locked, in a way that xml:id can't be
changed and is assigned to an empty string. Is this a normal behaviour? (PS:
this occurs before the insertion of the cloned element with insertBefore.)
I don't understand what a 'locked' element means, I don't see why you
should not be able to fix the xml:id on a copied element. seems
specific to gdome.
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel veillard com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]