From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] immediate evaluation of js on appendChild
Date: Fri, 17 Jun 2016 12:48:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1606171237550.8162@carhart.net> (raw)
In-Reply-To: <20160516220029.eklhad@comcast.net>
Hi Karl
> If my life crises abbate
I hope they do. Here's to better times.
> Kevin thanks for uncovering this.
You are welcome! It's good that the users have been
submitting problems, because this got me rolling and
now I have the itch to get something out the door.
I have found a few different corrections which I need to
write up and submit.
> The key here is, I think, when we design the new Iframe object,
> that Iframe.contentDocument.write() somehow invokes the innerHTML
> machinery.
Aha! That makes sense. Hook into the existing innerHTML
machinery and take advantage of it.
Kevin
prev parent reply other threads:[~2016-06-17 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 4:17 Kevin Carhart
[not found] ` <20160515130957.eklhad@comcast.net>
2016-06-15 23:27 ` Kevin Carhart
2016-06-17 2:00 ` Karl Dahlke
2016-06-17 19:48 ` Kevin Carhart [this message]
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=alpine.LRH.2.03.1606171237550.8162@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).