edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
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: Wed, 15 Jun 2016 16:27:31 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1606151609110.29301@carhart.net> (raw)
In-Reply-To: <20160515130957.eklhad@comcast.net>



Hi Karl
Yes.... could you go to http://carhart.net/~kevin/immediate.html?
In edbrowse nothing will happen so please 'ub' for the HTML source.
Now if I bail out and try it in my firefox, 
the alert will fire.  I'm not sure precisely which line it occurs on.  But 
there is not an eval() in javascript, so I think there must be evaluation 
supplied by the DOM.

I believe this is the purpose of the iframe formulation in the google 
groups page we were talking about a while ago.  immediate.html is a 
simpler version of the construction that they use.  Since google is doing 
it, it may be a common phrasing.  Question for Steven Terpe if you're 
around: I think you said you recognized the phrasing
frame.contentDocument.open();
frame.contentDocument.write(html);
frame.contentDocument.close();
Do you know if this is used a lot?

thanks
Kevin



On Wed, 15 Jun 2016, Karl Dahlke wrote:

> Is there some simple js you could whip up and post,
> as an example, so I know what you're talking about?
>
> Karl Dahlke
>

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

  parent reply	other threads:[~2016-06-15 23:26 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 [this message]
2016-06-17  2:00 ` Karl Dahlke
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=alpine.LRH.2.03.1606151609110.29301@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).