From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out.smtp-auth.no-ip.com (out.smtp-auth.no-ip.com [8.23.224.60]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 9259A79E0B for ; Tue, 27 Dec 2016 11:46:46 -0800 (PST) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 24C2F57A; Tue, 27 Dec 2016 11:47:10 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id uBRJl9wr005646; Tue, 27 Dec 2016 11:47:09 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id uBRJl8Uk005643; Tue, 27 Dec 2016 11:47:08 -0800 Date: Tue, 27 Dec 2016 11:47:08 -0800 (PST) From: Kevin Carhart To: Adam Thompson cc: Karl Dahlke , Edbrowse-dev@lists.the-brannons.com In-Reply-To: <20161227191126.GD8364@odin> Message-ID: References: <20161029110356.eklhad@comcast.net> <20161225130639.GB16190@odin> <20161126095227.eklhad@comcast.net> <20161227191126.GD8364@odin> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Edbrowse-dev] $ object in javascript X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.23 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2016 19:46:46 -0000 Hi Adam > > It depends on time zones etc, but I've certainly got time this week. Great - I am around also. Maybe let's get calibrated and this will supercede confusion over the time zones. Right now it's 11:30 AM in California. When I sit down to try to do something, I generally resort to fixing cases from the inside out. Do you think it would be good to take a set of tests like Acid3 and work off of that? It seems like we need an intermediate point which is both an implementation of the spec approach, but also gives you a series of specific things to say "this passed," "this failed." Find-and-fix has problems because it's just one thing after the next, forever, with no way of knowing if you have ten or a hundred remaining. Going to the W3 consortium and getting the spec document has problems because it is hard to know where to begin or how to translate what you're reading into an attainable task. thanks Kevin