From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] duktape and jsrt
Date: Thu, 13 Jul 2017 23:25:41 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1707132258360.14469@carhart.net> (raw)
In-Reply-To: <20170613180334.eklhad@comcast.net>
Among these many interesting points number five caught my ear:
> 5. Interwindow communication seems possible, based on just a few sentences from the programmers guide.
Gee! Are you referencing what I think you're referencing, namely
communication between window.document and an iframe's
contentWindow.contentDocument? In other words, we have this pivotal
utility function that is relied on by a lot of the tests in
acid3.acidtests.org:
function getTestDocument() {
var iframe = document.getElementById("selectors");
var doc = iframe.contentDocument;
for (var i = doc.documentElement.childNodes.length-1; i >= 0; i -= 1)
doc.documentElement.removeChild(doc.documentElement.childNodes[i]);
doc.documentElement.appendChild(doc.createElement('head'));
doc.documentElement.firstChild.appendChild(doc.createElement('title'));
doc.documentElement.appendChild(doc.createElement('body'));
return doc;
}
And we had set it aside, so is this back on the table thanks to duktape?
If so, that's great. If not, it sounds like duktape is great anyhow, and
thank you for doing all of this work on porting.
Kevin
next prev parent reply other threads:[~2017-07-14 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 22:03 Karl Dahlke
2017-07-14 6:25 ` Kevin Carhart [this message]
2017-07-14 20:17 ` Karl Dahlke
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.1707132258360.14469@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).