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 CBFC17913E for ; Tue, 27 Dec 2016 12:44:41 -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 9C2F73A6; Tue, 27 Dec 2016 12:45:05 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id uBRKj4Hh031074; Tue, 27 Dec 2016 12:45:04 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id uBRKj49t031068; Tue, 27 Dec 2016 12:45:04 -0800 Date: Tue, 27 Dec 2016 12:45:04 -0800 (PST) From: Kevin Carhart To: Karl Dahlke cc: Edbrowse-dev@lists.the-brannons.com In-Reply-To: <20161127151106.eklhad@comcast.net> Message-ID: References: <20161029110356.eklhad@comcast.net> <20161127151106.eklhad@comcast.net> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: [Edbrowse-dev] nextSibling and previousSibling 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 20:44:41 -0000 Hi Karl I remember you mentioning NASA, so I will try to solve it. Hang on, here is a very concrete idea! I know we need nextSibling and previousSibling. Does anyone want to take them, and if not, I'm going to make an artificial deadline that I'm going to try to get nextSibling and previousSibling out by the end of Wednesday! Then I will feel as though I haven't bunted. We just have to grab bits like this. I think implementing types of manipulations may be superior to starting with a site, because if you implement three manipulations, go back to the site and it magically works, you have fixed a root cause with broad implications and have not needed to care about a NASA developer's *own* middle layer of business logic and variables and style quirks, which takes time of its own and learning *that* stuff does not extrapolate at all. So that would be my argument for favoring the spec down - it could save a lot of time. Though just like I said above, I'm sure it's a back and forth, and you're trying to loosen up a logjam by two different means, poke over here with a case, prod over there with a DOM concept. Once it's done it's done. Sibling code in the next 48 hours, or bust! Kevin On Tue, 27 Dec 2016, Karl Dahlke wrote: > Implementing the spec is valuable, or at the very least reading the spec, > so that the piece you decide to implement, you're implementing it right! > But I do believe, with the above caveat, that find&fix is the biggest bang for the buck, and we don't have a lot of resources here, so on we go. > (I sometimes wonder how many fulltime programmers maintain chrome or edge or whatever.) > > I think we need to amass a list of sites that people want, that just don't work. > That's a market driven approach. > Kevin is already doing that; he has 2 or 3 that people have asked about, > that he is looking into. > My latest pet pieve is an entire domain, nasa.gov. > I'm a big space fan, and I love to read the articles, > but every page comes up blank, with or without js. > Didn't use to; the site use to be very accessible. > Not any more. > That's the problem with edbrowse, if you're not swimming forward you're falling behind. > I also can't listen to nasa tv with realplayer, though I could before. > That's another story. > Anyways, Kevin, you might add nasa.gov to the list of desirable and unworkable pages. > > Karl Dahlke > -------- Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists