Ok, since r1433 MochiKit.DOM.isParent is no more.
/Per
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group,
Hm, if I read the code correctly, then there is another difference,
namely that isChildNode also returns true if the second node is not the
direct parent, but also for grandparents and any ancestors. So it should
be actually renamed to something like isDescendant or isAncestor.
You can merge
Attempting two answers in one below...
On Sat, Oct 18, 2008 at 12:23 AM, Jason Bunting
[EMAIL PROTECTED] wrote:
Who is Noone? :P
Sigh... The endless joys we bring you native English speakers... ;-)
On Sat, Oct 18, 2008 at 5:54 PM, Christoph Zwerschke [EMAIL PROTECTED] wrote:
Hm, if I read
Per Cederberg wrote:
Both actually do that.
Ah, right. Overlooked the recursive call in the last line of isParent.
Then both names are really misleading. It's completely unusual to call a
not direct ancestor parent or a not direct descendant child.
And there's really no reason to keep them
Noone has opinions on this?
Cheers,
/Per
On Wed, Oct 8, 2008 at 3:51 PM, Per Cederberg [EMAIL PROTECTED] wrote:
The two functions MochiKit.DOM.isChildNode and isParent have both been
added in version 1.4 of MochiKit (not yet stable). But they are
virtually identical (except for a few bugs
it is worth.
Jason Bunting
-Original Message-
From: mochikit@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Per Cederberg
Sent: Friday, October 17, 2008 2:29 PM
To: MochiKit
Subject: [mochikit] Re: MochiKit.DOM.isChildNode and isParent
Noone has opinions on this?
Cheers
