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: [Edbrowse-dev] contentWindow
Date: Mon, 4 Sep 2017 19:15:34 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1709041859110.28685@carhart.net> (raw)
In-Reply-To: <20170804131018.eklhad@comcast.net>



I think there is a divergence based on whether the iframe is coming from 
html or created within js.  If I use the iframe in jsrt, it works.  But if 
I play along with how an iframe is created in the jquery.js code that I 
referenced, I think the contentWindow is not a window and doesn't have 
.document.  Is it a goof that the line in jsNode uses t->jv?  Or not!  It 
could be deliberate and a part of the whole.  I can't tell.    Here's my 
transcript that shows not working, followed by working.  Asterisks added 
to offset my input from the responses.

* b {any website with JS and jquery}
...
* jdb
* x1 = jQuery( "<iframe frameborder='0' width='0' height='0'/>")
[object Object]
* ok(x1)
0,length
* x2 = x1[0]
[object Object]
* ok(x2)
childNodes,style,className,class,nodeValue,attributes,ownerDocument,nodeName,nodeType,innerHTML,inner$HTML,contentDocument,content$Document,contentWindow,content$Window,parentNode
* x2.contentWindow
[object Object]
* ok(x2.contentWindow)
childNodes,style,className,class,nodeValue,attributes,ownerDocument,nodeName,parentNode,innerHTML,inner$HTML
* x2.nodeName
iframe
* x1.contentWindow.document
jdb line 1: TypeError: cannot read property 'document' of undefined
* .
bye
* b jsrt
22878
628
* jdb
* x1 = document.getElementsByTagName("iframe")
[object Object]
* x1
[object Object]
* ok(x1)
0
* x2 = x1[0]
[object Object]
* ok(x2)
childNodes,style,className,class,nodeValue,attributes,ownerDocument,src,nodeName,onload,nodeType,parentNode,innerHTML,inner$HTML,contentDocument,content$Document,contentWindow,content$Window
* x2.contentWindow.document
fetch frame http://www.edbrowse.org/jsfrm {it succeeds from here}


  reply	other threads:[~2017-09-05  2:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04  2:38 [Edbrowse-dev] suggested additions Kevin Carhart
2017-09-04 14:12 ` Karl Dahlke
2017-09-05  1:16   ` Kevin Carhart
2017-09-05  2:27     ` Karl Dahlke
2017-09-04 15:06 ` Karl Dahlke
2017-09-05  1:32   ` Kevin Carhart
2017-09-04 17:10 ` Karl Dahlke
2017-09-05  2:15   ` Kevin Carhart [this message]
     [not found]     ` <20170804223729.eklhad@comcast.net>
2017-09-05  2:58       ` [Edbrowse-dev] contentWindow Kevin Carhart
     [not found]         ` <20170804232757.eklhad@comcast.net>
2017-09-05  3:57           ` 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.1709041859110.28685@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).