From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.61]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 87E10796ED for ; Sat, 2 Jul 2016 15:10:20 -0700 (PDT) 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 E4EC1400C6D; Sat, 2 Jul 2016 15:11:59 -0700 (PDT) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id u62MBww9002031; Sat, 2 Jul 2016 15:11:59 -0700 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id u62MBwd1002024; Sat, 2 Jul 2016 15:11:58 -0700 Date: Sat, 2 Jul 2016 15:11:58 -0700 (PDT) From: Kevin Carhart To: Adam Thompson cc: Karl Dahlke , edbrowse-dev@lists.the-brannons.com In-Reply-To: <20160702164833.GA13590@odin> Message-ID: References: <20160523124137.eklhad@comcast.net> <20160702164833.GA13590@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] questions about new finds X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 22:10:20 -0000 Hi Adam and Chris, There's a lot to do basically. I see tidy errors, but I gravitate to the JS errors, I guess partially because they are autonomous for us to fix, while messages from tidy involve making threads with the tidy developers, fun and worthy in its own right, but the path of least resistance takes you to something you can work on right away. (Dang, here's a toast to the tidy group! It underpins everything now and it's so good I don't think about it! We only integrated tidy around 1 year ago.) We could add things to availableTags one by one as we find them but this will go forever. I experimented adding a "placeholder" to availableTags and editing html.c so that if the call to newTag fails to find a string, it will create your element as a "placeholder." But I don't know what I'm doing - I was also seeing some infinite loops in renderNode, which I probably caused by adding placeholder. I don't know what the TAGACT or flags should be for a made-up placeholder. K On Sat, 2 Jul 2016, Adam Thompson wrote: > Hi all, > > First of all appologies for going silent for a while; work, life and computer issues basically. > > On Sun, Jun 26, 2016 at 11:39:49PM -0700, Kevin Carhart wrote: >> >>> (1) Do you mean in the html text or createElement("modernizer")? >>> Those are radically different issues. >>> The first is up to tidy, and out of our hands. > What do we do in the first case, i.e. if we get ? If it's something we don't know are we putting it in the DOM but not rendering, or ignoring it? > Also, I think *some* of those tags are actually html 5 tags i.e.