From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 0D110789FE for ; Sun, 3 Jul 2016 04:12:31 -0700 (PDT) Received: by mail-wm0-x236.google.com with SMTP id f126so73290062wma.1 for ; Sun, 03 Jul 2016 04:14:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=GCa/TTjcsPqDw8Lew3OidW1026yf6mxN29c0FqcOz34=; b=Zi0/nEk5DXIZnecmaeao/KvMXJCPCpRyijAmVruaHAiPDY8bKT3C5gHme0O/2cphT7 rTcy1jTiehRaY/UDR6LNXFtuSRy/K7wXn4iJnk+9inXzcXZ06mn97SW/N4A9h49SDvC1 EXXhEx7eo02kYmArrtpNlP9fBMQ7MuMhT5WG4a6UFAmIGgdPamR23brCDVPx1s6BtsjK ddBM9Wv0XYGEzy3gs0r3qLoPC9BLgs3+bBuqnJez1fquXoQ2UaXjb13fnSnCi7R6Pnyc bv2DS0pLFc4DiKm4RK3yrwTiN8/9UdkMmlw2Bn27+3EMYZMVpkPO3kAkJTbnV/WEsb41 PAqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=GCa/TTjcsPqDw8Lew3OidW1026yf6mxN29c0FqcOz34=; b=KCaRj4dqoEbNq3eONFtpPPRn4wuwCVNjNTEuvzyj20eXXQ68c3QIMkPsGlo+UOW2l8 gWBnMQQ7b1924z4sR2BdjUzcl1p7nCFoaNyGXx5m3UJLCit6DkX8vkg0NuiXHweJ+el5 XnnUXGvtSD9N+OSSpkSqgGMNAKK2fr0R6yYLY6BzFf8UDULtH9O1TXKHXqbvTQTKesNK QAL7zs1sV5UCVhEnv1zU0TzKArIaYdN1DC7Wk0xxMo90wXtxMIyKarAgD+gu/o+9aRMZ mw6UTnqXSmsH0iiMOkwFUhopbO9G5nNg6KRHAc8begBEFGjZeWjHsSa74M1F74ubpXCH uL8w== X-Gm-Message-State: ALyK8tJ8UhxWbRL0bSboctsVI+du+cOYjbtWQ/TGm5h59XE6dnROmvPw+XhRUOGlwfp/5Q== X-Received: by 10.28.209.13 with SMTP id i13mr6386429wmg.93.1467544450998; Sun, 03 Jul 2016 04:14:10 -0700 (PDT) Received: from odin (odin.sdf-eu.org. [178.63.35.194]) by smtp.gmail.com with ESMTPSA id r127sm55942wmf.21.2016.07.03.04.14.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jul 2016 04:14:10 -0700 (PDT) Date: Sun, 3 Jul 2016 11:12:05 +0000 From: Adam Thompson To: Kevin Carhart Cc: Karl Dahlke , edbrowse-dev@lists.the-brannons.com Message-ID: <20160703111205.GC19967@odin> References: <20160523124137.eklhad@comcast.net> <20160702164833.GA13590@odin> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hOcCNbCCxyk/YU74" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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: Sun, 03 Jul 2016 11:12:31 -0000 --hOcCNbCCxyk/YU74 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jul 02, 2016 at 03:11:58PM -0700, Kevin Carhart wrote: > 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.) Agreed, it's worked well and simplified the code-base as well as handling much of the oddness in modern html for us. > 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. I think that we should probably treat them as... div... elements may be so at least things are rendered. May be print a debug message at a relatively high debug level so that we can track unimplemented tags and hopefully clean up some of the more common ones. The trick here is (as I said in a previous email to Karl) to expose the provided element type to js. In some cases, i.e. with non-text elements, this may not necessarily be possible but I suspect that doing this will hopefully fix a few things with just one task. Cheers, Adam. --hOcCNbCCxyk/YU74 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXePMFAAoJED6sZNk+oYF/eoUP/jUu3gy4zoceD2V4BsHRvAYW Vht50XFRK34q+cYWFrfFYu5zJeIQAS7c6QA2I50g/YReSNefG5/tBQkAbYu0juju 3txOrOgvP5PzuwlDLqeu/sD1C+5m0KQ9P+BljKlJZGG0HmlNktX+8aDlEYe3BGlw lbdDg8DeQPbXkEtmQ2jOtAZIiHTsjTxu82EXJNff2m49MuOm32GtW6Kxn4dkI8AZ iOuJO6ULWiH2qABwB0MxrJAVnZsSQ5FBUOx/QFmnIpSJAE05Yhq+infOJ8gfLuWL ReQGeL462NggIWOFEL+28b5bJMSXKNVin+mk/FBtNL38dgdUDsWxncsrX0SIqgCS KZxbTfGAL089L+fxq9OuDi4GkumDr7WYcVFFDxonqO+c0EwWC4KepFO13PLmREBC xHBUiZP2bgl+OIlOJmF6X8sD2UsU/pdEK/QcFhk48tzO6ErYNQJmj3rF40mNM/hK s2EZsV1r8FrBMOedVKRBMXCg3ujzTYpnWZtX0GembvOGK7q7H5u/HR3IYVXwc/BI 3ysMCjpdP5zrHiO303s2jYI9hrzTQUtW72p7fVcu/l7lKb0jST7Z12aBwO/113X0 55t0nR+LwzX3rdHw8Zl6mNVOqAtGTgWFhu3O63dBsoMoXh2Q0TOn7tFbnWxv3pky cL+/dpb1kf+YBRIDA4ZW =rUbU -----END PGP SIGNATURE----- --hOcCNbCCxyk/YU74--