From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.61]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 3DE5621DE01 for ; Thu, 24 Mar 2016 00:52:35 -0700 (PDT) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 862F04009D7 for ; Thu, 24 Mar 2016 00:52:50 -0700 (PDT) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id u2O7qnC5029643 for ; Thu, 24 Mar 2016 00:52:49 -0700 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id u2O7qnfB029639 for ; Thu, 24 Mar 2016 00:52:49 -0700 Date: Thu, 24 Mar 2016 00:52:49 -0700 (PDT) From: Kevin Carhart To: Edbrowse-dev@lists.the-brannons.com Message-ID: User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463766271-576411684-1458805969=:15001" Subject: Re: [Edbrowse-dev] frames and iframes (fwd) X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.21 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 07:52:35 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463766271-576411684-1458805969=:15001 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT 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 To: Kevin Carhart 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(‘Some document as text ’) iframe.contentDocument.close() you’ll often see it done `iframe.contentWindow.document.open()`. > On Mar 22, 2016, at 11:23 PM, Kevin Carhart 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 > Edbrowse-dev@lists.the-brannons.com > http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev ---1463766271-576411684-1458805969=:15001--