From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] Gopher item type 7
Date: Thu, 22 Aug 2019 15:55:55 -0400 [thread overview]
Message-ID: <20190722155555.eklhad@comcast.net> (raw)
In-Reply-To: <20190822174628.GE16219@toaster>
> When entering keywords in the newly rendered form they vanished after a
> rerender event.
Wow, this is a much bigger problem.
jsrt is my test run, along with acid3, but I sometimes, often, forget to run jsrt with js disabled.
If you do, none of the form elements stick.
I don't remember this behavior before so must have done something bad in the last couple months.
Karl Dahlke
next prev parent reply other threads:[~2019-08-22 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 17:46 Adam Thompson
2019-08-22 19:55 ` Karl Dahlke [this message]
2019-08-22 20:10 ` 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=20190722155555.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).