Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/30/2007 11:01:21 PM:
> Thanks for the clarification. Now someone on the Xerces team just
> needs to put the issue in its proper resolution state and this should
> be all cleared up.
Done.
> Jake
>
> At 01:45 PM 1/30/2007, you wrote:
>
> >Posted my
Thanks for the clarification. Now someone on the Xerces team just
needs to put the issue in its proper resolution state and this should
be all cleared up.
Jake
At 01:45 PM 1/30/2007, you wrote:
Posted my understanding of this into that Jira entry. If anyone has
doubts, checking with the D
Posted my understanding of this into that Jira entry. If anyone has doubts,
checking with the DOM WG rather than taking my word for it would be
perfectly reasonable.
I didn't close the issue because I'm no longer part of the core Xerces
development team, so it shouldn't be my call. The Xerces DOM
Ok, then please make this statement official and update Elliotte Rusty Harold's
longstanding "cloneNode forgets IDness of attribute" [1] issue as
"resolved/invalid", unless you make some sort of distinction between
importNode()/adoptNode() and cloneNode(). If you made a distinction, please
explai
> Joe-user expects an ID that
> exists the source document to continue to exist in the destination
document,
> especially when the two documents use the same schema.
Correction: You expect it. Not everyone does. Not everyone wants it. That's
a clear argument for the DOM not doing it unless told t
Quoting Michael Glavassevich <[EMAIL PROTECTED]>:
> Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/29/2007 02:02:41 PM:
>
> > Quoting Michael Glavassevich <[EMAIL PROTECTED]>:
> >
> > > Hi Jake,
> > >
> > > Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/28/2007 03:50:25 AM:
> > >
> > > > I just realize
Doesn't this discussion hinge on what confers IDness?
Among the various possibilities are these:
1. You're copying nodes from a namespace-aware document conforming to
a schema which defines certain attributes as having type ID, into a
document governed by the same schema or one which imports th
Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/29/2007 02:02:41 PM:
> Quoting Michael Glavassevich <[EMAIL PROTECTED]>:
>
> > Hi Jake,
> >
> > Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/28/2007 03:50:25 AM:
> >
> > > I just realized the Elliotte Rusty Harold posted an issue about
> > > losing ID'ne
Quoting Michael Glavassevich <[EMAIL PROTECTED]>:
> Hi Jake,
>
> Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/28/2007 03:50:25 AM:
>
> > I just realized the Elliotte Rusty Harold posted an issue about
> > losing ID'ness when cloning [1]. Since the importNode()/adoptNode()
> > issue is so related,
Hi Jake,
Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/28/2007 03:50:25 AM:
> I just realized the Elliotte Rusty Harold posted an issue about
> losing ID'ness when cloning [1]. Since the importNode()/adoptNode()
> issue is so related, I posted a comment about there rather than
> reporting a ne
At 02:50 AM 1/28/2007, you wrote:
>
>I just realized the Elliotte Rusty Harold posted an issue about
>losing ID'ness when cloning [1]. Since the importNode()/adoptNode()
>issue is so related, I posted a comment about there rather than
>reporting a new issue. I also attached a patch, which works
I just realized the Elliotte Rusty Harold posted an issue about
losing ID'ness when cloning [1]. Since the importNode()/adoptNode()
issue is so related, I posted a comment about there rather than
reporting a new issue. I also attached a patch, which works for me
in limited testing, to tran
Quoting Michael Glavassevich <[EMAIL PROTECTED]>:
> Hi Jake,
>
> Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/25/2007 01:19:46 AM:
>
> > I'm wondering whether or not I should expect that if I import/adopt a
> > node from a source DOM, that attributes of type ID on the
> > imported/adopted nodes sho
Whoops, please ignore what I said about the HTML DOM. In fact, a custom variant
of the standard DOM was being used. The HTML DOM works fine because of the
fallback recursing of the document looking for elements with an attribute named
"id" with the given value if super.getElementById("myId") fai
Hi Jake,
Jacob Kjome <[EMAIL PROTECTED]> wrote on 01/25/2007 01:19:46 AM:
> I'm wondering whether or not I should expect that if I import/adopt a
> node from a source DOM, that attributes of type ID on the
> imported/adopted nodes should be found by getElementById() in the
> destination DOM.
I'm wondering whether or not I should expect that if I import/adopt a
node from a source DOM, that attributes of type ID on the
imported/adopted nodes should be found by getElementById() in the
destination DOM. The behavior I'm seeing is that getElementById()
fails to find the elemements (nu
16 matches
Mail list logo
