From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 6443279046 for ; Tue, 3 Nov 2015 00:01:46 -0800 (PST) Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-01v.sys.comcast.net with comcast id cw261r0082AWL2D01w262v; Tue, 03 Nov 2015 08:02:06 +0000 Received: from eklhad ([IPv6:2601:405:4080:53:21e:4fff:fec2:a0f1]) by resomta-ch2-04v.sys.comcast.net with comcast id cw251r00B1DsNmD01w26Ma; Tue, 03 Nov 2015 08:02:06 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151002184159.eklhad@comcast.net> User-Agent: edbrowse/3.5.4.2+ Date: Tue, 03 Nov 2015 03:02:05 -0500 Message-ID: <20151003030205.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1446537726; bh=MnW3P+3vWJHkC9clE1loVTTLSfZc/iVXlRRmfT/veKg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=UPiICMLKxgnggk+aR93xpuDSiTo0dIi16CwsczDr70c8qVHw/wIylvNb003ytoRwt 1P01XN/YS2upyT5oS7AjqLy5eEHR+r4FYGr/ghSVUX3jY9/A+oIyXuWlYhJrzivpcP PhMDGEWSJobhC10aRWg+lBVZunjzJcSQYVHpXozs1hNXUj6TKvxGaxH+aQo87HLykY Pfgji3Ov2LfvOtgdjL9ulebjxr9woI9MsfNHltbtDOL0vJ4RQvZ18iu1GJZozqJUZc /OIvD7/SHClFrf+zk+LRcHZh+Toz9S41esi6fK2MyABYVrMB+KKj/tFE43UCT2Vpds 2s7gYj3027psQ== Subject: [Edbrowse-dev] Red Hot X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2015 08:01:46 -0000 Always investigate every mystery. It's always trying to tell us something. This infinite loop is caused by: for(;e.firstChild;) e.removeChild(e.firstChild); Clearing all the nodes out from under e, simple enough, but I implemented firstChild as a function, e.firstChild(), so e.firstChild is always true. Oops. firstChild is a property, a magic property that always means this.childNodes[0]. Wow, how can we implement that? Well there's a way, and it doesn't require native code, thank heaven, but I will need to muck with all the firstChilds in starrtwindow.js, so I think I'll hold off until Kevin sends me his next cloneNode. Karl Dahlke