From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2001:5c0:1111:6c00:21b:b9ff:feee:aa45]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 0EDE09FEFC for ; Wed, 2 Nov 2011 05:46:11 -0500 (CDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20110931193027.eklhad@comcast.net> Date: Wed, 02 Nov 2011 05:48:33 -0500 In-Reply-To: <20110931193027.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 31 Oct 2011 19:30:27 -0400") Message-ID: <877h3ilrzy.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Edbrowse-dev] [Bug#647226: edbrowse: button press does not... X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.14 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 10:46:12 -0000 Karl Dahlke writes: > Here is what has confused me from the start. > How to make javascript march on even if something is undefined. The problem with just blindly marching on is that errors can cascade. Have you ever seen a shell script fail because one of its component commands is undefined? It just keeps trudging. Sometimes, it can get pretty ugly, as failure begets failure. This is one of the numerous things I dislike about shell scripting. Your point is a good one, though, and it bares investigating. Maybe the best approach is to go digging around in the firefox source. That's a scary prospect, though. -- Chris