From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Radio Caroline wants doc.implementation
Date: Mon, 25 Sep 2017 19:53:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709251945250.7788@carhart.net> (raw)
In-Reply-To: <20170825084643.eklhad@comcast.net>
Thank you! Do you know what it's for? It seems redundant with something
else, like what does it provide that
iframe.contentDocument doesn't? And why is there
something called implementation to manage it?
Maybe ours is not to reason why.
On Mon, 25 Sep 2017, Karl Dahlke wrote:
> Ok, implementation.createHTMLDocument is implemented as best I understand it,
> and the sample program in
> https://developer.mozilla.org/en-US/docs/Web/API/DOMImplementation/createHTMLDocument
> runs properly.
> Now radio caroline moves on to something else and generates lots of "cannot fetch local javascript" messages,
> which means it has gone somewhere wherein it is not calling resolveURL to turn that relative path into an absolute url.
> Must be down in the next xhr or something...
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2017-09-26 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 5:45 Kevin Carhart
2017-09-25 12:46 ` Karl Dahlke
2017-09-26 2:53 ` Kevin Carhart [this message]
2017-09-26 4:01 ` Karl Dahlke
2017-09-26 5:50 ` [Edbrowse-dev] fetch local / progress on carrier lookup Kevin Carhart
2017-09-26 11:57 ` Karl Dahlke
2017-09-26 23:29 ` [Edbrowse-dev] freecarrierlookup 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.1709251945250.7788@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
/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).