From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 12808789A7 for ; Sun, 4 Jan 2015 05:17:38 -0800 (PST) Received: by mail-we0-f179.google.com with SMTP id q59so6494922wes.38 for ; Sun, 04 Jan 2015 05:15:13 -0800 (PST) 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-type:content-disposition:in-reply-to:user-agent; bh=YB1+DOwf80FGP/OtUUsXR/Kirsr2XhrGA5xdynQaZtw=; b=Q0vE5LD2rhYwaUGQ4T3Bg1fMArAMFe0EEIMtApiVtSYhUZAqwbUpfeU32VmmBVX0hv Tv/JBLq3NcQnBNLYcUCB9VarKp4JaMNNGnC/MAXYFwkrQcZEaWPuEjBsv+94+ZpbPQil b2lkpjzEL0jgas03Z2azLqMcKjQR4Dz6sisf5XvF8CXGnMHzRe2eLlK5/AbORWcSFhsZ 5xLWzrp+u0qvR0My2g4qjOrhQiEu6CF2VlM0hOjb1hUqs5QLLiPDiOLJaUVNwvh4aTre nLesR5bl2A2Lokfdea7lBWZgWa9Mb6pUSs7//qlctHXdfljjWKs7HMZciOvwMWmSFsdY UikQ== X-Received: by 10.180.73.206 with SMTP id n14mr15971922wiv.60.1420377313326; Sun, 04 Jan 2015 05:15:13 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id fm10sm6038815wib.7.2015.01.04.05.15.11 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Jan 2015 05:15:12 -0800 (PST) Date: Sun, 4 Jan 2015 13:15:05 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20150104131505.GA31364@toaster.adamthompson.me.uk> References: <20150003103402.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <20150003103402.eklhad@comcast.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Edbrowse-dev@lists.the-brannons.com Subject: [Edbrowse-dev] multi-pass html rendering X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2015 13:17:38 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jan 03, 2015 at 10:34:02AM -0500, Karl Dahlke wrote: > My next project, which is not a major redisign, > but more like filling in some holes, > is to fix tag.innerHTML = "foobar", in js. > This never really worked properly, never. > It injects html into the page, after it is parsed, > but my parsing software in html.c was built to be a one time thing, > so there is some work to do here. > I use to get around this by dumping the injected html into another buffer > and rendering it there, but that is ugly. > It belongs where it belongs, under the specified tag > on the current page. > And for calls to document.write() after browse, I use to do the same thing, > dump the html somewhere else and parse it in a separate window. > This is illustrated by line 3 in browsed jsrt, the timer, fire it and > watch what it does, ugly. > It should just append that (rendered) html to the current buffer. > Both issues are related, and I am making a series of small foundational > changes that will let me approach this one. That's good. It'll be nice to get this sorted, and hopefully it may make some things work more as expected (I'm not sure what currently happens if js expects the inner html to be present in the current page, but that'll no longer be an issue hopefully). What kind of "foundational changes" are being made, and will the multi-pass rendering logic be able to also handle other js-made dom changes or is it going to be more like altering the html string in memory then re-rendering that? In addition, will the dom be altered by the presence of this html whilst the script is running or will the script run then the new html be parsed and linked in? I'd think the first is the expected behavior, but I'm not sure. Cheers, Adam. --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUqTzZAAoJELZ22lNQBzHOlVoH/2JBbodUBBm17YYAxFmbKdip ADQHYY1WmRcMjVnje0/NV7l7vwliixTEH4n6Adfrh7tA9JL4uEp6tieVRwvenkmy pIZaVM6+lNDFrMK6ZiJ91dduFKf71y+qyhTopqtam9rCoMGi7SHQIPhp/Buc/ZZ9 qRL+1dQclyOKPfcbIc3YPzqO3otNfixkGMes1gtMtHiFBp/AeTBSMTvSPtayfW1G TXiQj7wEECnQzDJu/INy1KU9FZRQLwbdaQ3aCniEuKlAyEWgrMFL+tR0pdvqdIy1 ppmb5yEB8PbWC3nyjLrfaiAX6FPsU+BgWrqzunHwCvw4FXQ76nfZf0FdVyMfhnU= =LubT -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk--