edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  immediate evaluation of js on appendChild
Date: Thu, 16 Jun 2016 22:00:29 -0400	[thread overview]
Message-ID: <20160516220029.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1606142050180.31841@carhart.net>

> frame.contentDocument.write(html);

The key here is, I think, when we design the new Iframe object,
that Iframe.contentDocument.write() somehow invokes the innerHTML machinery.
That parses and executes html immediately,
though if that html has <script> as in your example,
the script might not run immediately, as another script is already running,
but I don't think that's a problem,
as long as the html dom objects are created immediately, which they are,
because innerHTML requires that as we already saw.
If my life crises abbate I'll work on this,
because I can see it really needs to be done,
and meantime I'll just advise on the design.

Kevin thanks for uncovering this.
I really think missing dom pieces and interactions are 90% of our
webpage troubles, while the really hard asynchronous ajax java methods etc
are only a small percentage of our troubles.
So filling in missing dom pieces, like Iframe, is probably
the biggest bang for the buck.

Karl Dahlke

  parent reply	other threads:[~2016-06-17  1:59 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 [this message]
2016-06-17 19:48   ` Kevin Carhart

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=20160516220029.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).