Thanks for the messages, Steven and Karl.
Steven mentioned that my phrasing was off - please see below for how it
should be instead.
Well, it seems like a can of worms. I am going to have to work on
something else for a couple of days, but this could be a very helpful area
to tackle. I'll put some time into this as soon as I can. There is no
great urgency, it is just a juicy problem. First raised by Sebastian,
then it was the impetus for tidy issue 348, and now we can use it as the
jumping off point for more.
My guess is that one reason edbrowse will not display actual discussion
threads on Sebastian's example page:
https://groups.google.com/forum/#!topic/boost-compute/xJS05dkQEJk
is because that stuff exists inside of an iframe.
This is one snippet of non-minified, D.V. javascript from google which I
have been working with and which is raising errors:
u(){if(s){return}var
a=o.createElement(T);a.src=U;a.id=O;a.style.cssText=V+W;
a.tabIndex=-1;o.body.appendChild(a);
s=a.contentDocument;
if(!s){s=a.contentWindow.document}s.open();var
b=document.compatMode==X?Y:Z;s.write(b+$);s.close()}
function v(k){function l(a){function b(){if(typeof o.readyState==_){return
typeof o.body!=_&&o.body!=null}return
/loaded|complete/.test(o.readyState)}
Near the top it says a = o.createElement(T)
o is document
T is an iframe, which gets assigned to a
After that, it wants to say
s = a.contentDocument;
s = a.contentWindow.document;
s.open()
You're right, Steven, it follows what you described. It's open() without
a parameter, and then there is a parameter to write(), followed by
close(). So I might be getting tripped up on some google ads library and
not know any better. However, this google groups page does not contain
any advertising at all so maybe the iframe is for real content after all?
thanks
Kevin
---------- Forwarded message ----------
Date: Wed, 23 Mar 2016 10:08:45
From: Steven Terpe <[email protected]>
To: Kevin Carhart <[email protected]>
Subject: Re: [Edbrowse-dev] frames and iframes
Hi Kevin,
`iframe.contentWindow.document === iframe.contentDocument` by reference.
I’ve never seen it like contentDocument.open(url). Don’t think that works — it
is to
open the document for writing, most often for ads.
ie.:
iframe = document.createElement(‘iframe’)
document.body.appendChild(iframe)
iframe.contentDocument.open()
iframe.contentDocument.write(‘<html>Some document as text </html>’)
iframe.contentDocument.close()
you’ll often see it done `iframe.contentWindow.document.open()`.
On Mar 22, 2016, at 11:23 PM, Kevin Carhart <[email protected]> wrote:
It's been quiet recently - I hope everyone is doing all right and is having a
good early 2016.
Thanks to Geoff's fix for tidy issue 348, fixing one thing exposes the next,
and the next thing in the Google Groups example involves an iframe.
Do we support iframes presently?
Apparently the following things exist:
iframe.contentWindow
iframe.contentDocument
and there is a syntax like:
iframe.contentDocument.open("url..")
iframe.contentDocument.close()
Is anyone already familiar with these behaviors? Are these essentially the
same as how a frame would behave?
I notice that if an iframe is created using document.createElement("iframe"),
it becomes TAGACT_FRAME. So are open, close, contentWindow and contentDocument also
found on frame, in a comparable fashion?
In case no one knows, thank you for reading and I will RTFM.
thanks
Kevin
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
