From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] Unresponsive edit buttons
Date: Sun, 19 Jan 2020 08:49:15 -0500 [thread overview]
Message-ID: <20200019084915.chuckhallenbeck@gmail.com> (raw)
Hi folks,
I am using edbrowse from the master branch on git,
and have encountered a problem with unresponsive buttons on www.storyworth.com,
where I have an account. My daughter, with a windows laptop,
also has access to the account, and has no problem activating the same buttons.
The buttons in question include a set of actions related to edit functions.
Here is an example involving a button called "edit title" which fails to activate,
after which I used the capital A command to view the underlying code.
* {Edit title}
A
A
32
,
<br><a href=''>
Edit title
</a>
I get the same behavior whether I log into the account with or without
the line nojs=storyworth.com in my config file.
Any suggestions are much appreciated.
Chuck
next reply other threads:[~2020-01-19 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 13:49 Chuck Hallenbeck [this message]
2020-01-24 18:34 ` Karl Dahlke
2020-01-19 14:18 Chuck Hallenbeck
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=20200019084915.chuckhallenbeck@gmail.com \
--to=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).