From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Radio Caroline wants doc.implementation
Date: Tue, 26 Sep 2017 00:01:59 -0400 [thread overview]
Message-ID: <20170826000159.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1709251945250.7788@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 258 bytes --]
I fixed the fetch local javascript bug.
It was subtle, executing scripts out of order, and in the wrong frames, wherein the base url was wrong and the url didn't resolve and blah blah blah.
Fortunately the fix was only a few lines of code.
Karl Dahlke
next prev parent reply other threads:[~2017-09-26 4:00 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
2017-09-26 4:01 ` Karl Dahlke [this message]
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=20170826000159.eklhad@comcast.net \
--to=eklhad@comcast.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).