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] master window
Date: Tue, 30 Jan 2018 21:18:38 -0500	[thread overview]
Message-ID: <20180030211838.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1801301729210.30377@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

> maybe the site has a library that mucks around with createElement

A really good guess. I hadn't thought of that.
Snag the old function, put yours in its place, and call the old one on traditional arguments.
So I gathered all the javascript from oranges.com, deminimized, and grepped for createElement.
document.createElement is never assigned anything. The site does not overload it.
It is, I assume, the base browser function.
We could test this by writing a little script and letting other browsers process it. What do they do?
Here are the unusual calls from oranges.com.

'<div class=\'' + j + '\' data-action=\'' + e + '\' data-send=\'false\' data-layout=\'' + g + '\' data-show-faces=\'false\' data-href=\'' + c + '\'></div>'
'<div class=\'' + j + '\' data-href=\'' + c + '\'></div>'
'<iframe name="' + e + '" ></iframe>'
'<iframe name="stLframe" allowTransparency="true" style="body{background:transparent;}" ></iframe>'
'<iframe name="stframe" allowTransparency="true" scrolling="no" frameBorder="0"></iframe>'

Karl Dahlke

      reply	other threads:[~2018-01-31  2:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  1:16 Karl Dahlke
2018-01-31  1:40 ` Kevin Carhart
2018-01-31  2:18   ` Karl Dahlke [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180030211838.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).