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] document.write atomic
Date: Tue, 29 Sep 2015 02:51:36 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1509290214500.5825@carhart.net> (raw)
In-Reply-To: <20150828232006.eklhad@comcast.net>



Crud.  To be honest, I really don't know.

It's true - your apples example shows document.write
building segments that don't make any sense on
their own.

It seemed to me that in my other example, well,
you have to interpret the jquery syntax to understand
it, but the point is that it says 'write', which
pumps in whatever is in div.innerHTML, and then
immediately afterwards, calls jquery's own
find() method on that html.

frameDoc.write(div.innerHTML);
var $bingImg=$(frameDoc).find("#minimap > img");

But of the two examples, I think you're correct,
because the use of jquery is probably a confound
whereas your apples landing page uses vanilla javascript.

The only thing that bothers me about taking sites.help.org
as a precedent is that they appear to be the ethically
challenged portion of the internet, and this might suggest
that they are less than technically airtight too.  For
instance, they make an iframe out of:

www.youtube-nocookie.com

Which is like a phishing trick to deceive you.

But does questionable intent necessarily mean that
their javascript was bad?!  Not necessarily but 
anyway, I will scout around a little more tomorrow
just to corroborate with a little more usage.

Kevin

      parent reply	other threads:[~2015-09-29  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  3:20 Karl Dahlke
2015-09-29  7:14 ` Adam Thompson
2015-09-29  9:51 ` 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.1509290214500.5825@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).