From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] V 3.5.4
Date: Sun, 10 May 2015 20:54:11 -0400 [thread overview]
Message-ID: <20150410205411.eklhad@comcast.net> (raw)
In-Reply-To: <87a8xcne4l.fsf@mushroom.localdomain>
> The only troubling bit is document.write /
I don't think this will be a problem.
We pass the web page html string to tidy, get the node tree back.
Run javascript for each <script> node.
When document.write is called, we have another html string.
Call tidy again, get a node tree back,
attach it to the <script> node that ran the javascript.
And continue.
Not much different from what I do today.
I call htmlParse() whenever I have html source to parse,
no matter where that html comes from.
Karl Dahlke
next prev parent reply other threads:[~2015-05-11 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 23:37 Karl Dahlke
2015-05-11 0:37 ` chris
2015-05-11 0:54 ` Karl Dahlke [this message]
2015-05-11 22:41 ` Adam Thompson
2015-05-11 23:23 ` Karl Dahlke
2015-05-12 7:32 ` Adam Thompson
2015-05-12 9:15 ` Karl Dahlke
2015-05-13 7:17 ` Adam Thompson
2015-05-13 8:16 ` Karl Dahlke
2015-05-13 13:15 ` Karl Dahlke
2015-05-14 7:03 ` Adam Thompson
2015-05-12 8:07 ` chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150410205411.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).