Subj : 
To   : netscape.public.mozilla.jseng
From : 
Date : Sun Jan 02 2005 03:39 pm

From: Peter Wilson <pwilson@gorge.net>
Newsgroups: netscape.public.mozilla.jseng
Subject: Re: Sharing Javascript objects between different XUL windows.
Date: Sun, 02 Jan 2005 14:59:57 -0800
Organization: Another Netscape Collabra Server User
Lines: 8
Message-ID: <cr9ueg$i9o1@ripley.netscape.com>
References: <cqdgbb$8kg1@ripley.netscape.com> <41CA6151.40000@meer.net>
NNTP-Posting-Host: ppp182-124.broadband.gorge.net
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
In-Reply-To: <41CA6151.40000@meer.net>
Xref: newsmst01a.news.prodigy.com netscape.public.mozilla.jseng:9607

I have made a discovery which may explain what is going on.

DOM3 has introduced a new function isSameNode(DOMNode) which returns 
true for the two DOM elements in question even though === is not true.

Having been away for some while I may have missed a fundamental change 
in the way Mozilla supports DOM processing internally. Previous 
assumptions about object identity may not be valid.

.