edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Cc: chuckhallenbeck@gmail.com
Subject: [edbrowse-dev] More NASA
Date: Wed, 06 Jun 2018 00:55:21 -0400	[thread overview]
Message-ID: <20180506005521.eklhad@comcast.net> (raw)

And I mean that literally!

Chuck mailed me about a couple of sites that are missing sections, relative to where they were a couple weeks ago.
bookshare.org for example.
It took several hours to track down the bug, but then, once found, only about 4 lines to fix.
So those sites should be back, but for grins I pulled up nasa.
In fact I need to do that before every commit, nasa is so easily broken.
Well it's been about 50 lines for the past few months, now it is 160.
There's a huge menu of 90 topics that wasn't there before.
So that's kinda cool. It's progress.
The link at the top is I think suppose to show or hide this panel of topics,
but it doesn't work, so I'll have to check into that as time permits.

Karl Dahlke

             reply	other threads:[~2018-06-06  4:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06  4:55 Karl Dahlke [this message]
2018-06-06  7:42 ` Kevin Carhart
2018-06-06  8:52   ` [edbrowse-dev] getBoundingClientRect 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=20180506005521.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=chuckhallenbeck@gmail.com \
    --cc=edbrowse-dev@edbrowse.org \
    /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).