From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by hurricane.the-brannons.com (Postfix) with ESMTP id D2CB678432 for ; Sun, 9 Feb 2014 06:19:23 -0800 (PST) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta01.westchester.pa.mail.comcast.net with comcast id QDzM1n00817dt5G51EJmzK; Sun, 09 Feb 2014 14:18:46 +0000 Received: from eklhad ([107.5.36.150]) by omta13.westchester.pa.mail.comcast.net with comcast id QEJl1n00B3EMmQj3ZEJlMm; Sun, 09 Feb 2014 14:18:46 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Sun, 09 Feb 2014 09:18:46 -0500 Message-ID: <20140109091846.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=q20121106; t=1391955526; bh=QoYVh9nutB1ApOGvVryyIb9nrDO9BHp29VSLYCcraOE=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=Ihk8RcGG7LhXzS6Zv+s0DRhVYn4iabcXE+FJhqYGXshetTrXUi60bAWEE6RJ1i3q1 i3OdvKLscz0lIiF0fQSNClKiNljCIRED2dcE3lz3czarzvvGcXVU1YsRHSa846rFzc 1/EULpno7OSsliMlOaJVc5W2QtSoBmghYqXrgHPin2pD77X7ilkTiT9gVe2ecp5Wl8 nNK/BltKXaMuZl3gsHIkG1tyY49emGQKt6pn5pig0LXYxIjbjH2LgtjFsqzFC0t/1z P1lWTlSQlbA7BtJ1KSCLc6vtoIxhIO+FIUbIMa7YMXdh7rjVxLOm1ATO36I5iJ43V7 goH3AFLiaT38g== Subject: [Edbrowse-dev] Error Legs X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Dahlke List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 14:19:24 -0000 > I'd still prefer it if it just killed the offending context as well I agree, and I might be the one to work on this - but that would be one of those major changes that I think we said we would wait on until our work was stable. I keep coming back round to the fact that if we can't get this to work with moz js 24 libraries as distributed, then edbrowse is dead anyways, except perhaps on our three machines. If it can't be distributed then I don't know how much time I should spend on it. I'm not trying to be Debbie Downer, just practical. We should be doing what we can to get it to function in the debian world. If that is both in process and/or on hold, or if one of you is taking that on, then I could work on error legs in parallel, and would be willing to do that, as it is a systemic change throughout. I just keep looking up and seeing the sword of damocles overhead. Karl Dahlke