From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nicolas Graner <nicolas.graner@universite-paris-saclay.fr>
Cc: 43218@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#43218: EWW handles default answer incorrectly when changing a select
Date: Sun, 06 Sep 2020 14:35:21 +0200 [thread overview]
Message-ID: <87zh63t75i.fsf@gnus.org> (raw)
In-Reply-To: <86pn6z3x7k.fsf@hypra-xx> (Nicolas Graner's message of "Sun, 06 Sep 2020 14:29:19 +0200")
Nicolas Graner <nicolas.graner@universite-paris-saclay.fr> writes:
> I agree. IMHO options should be presented like a list of checkboxes in a
> dedicated temporary buffer. In addition to multiple selections,
> advantages include:
>
> * no mabiguity if several options have same value and/or text
> * can handle option with empty text
> * can handle disabled options
> * present options in the order intended, not alphabetized as in
> minibuffer completions
> * search commands are available (userful if there are many options)
Those are good points... Dropping into a recursive-edit (in a new
temporary buffer) can be somewhat confusing for the user, though. (epa
does something similar when selecting a public key for encryption, and
it's less than perfect from a usability standpoint.)
> Couldn't a large part of the code for checkboxes/radio buttons be reused?
Probably.
It'd be nice if Emacs had a real drop-down in-buffer menu -- that's how
other browsers present a select box. Or has Emacs gotten that lately?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-06 12:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 10:44 bug#43218: EWW handles default answer incorrectly when changing a select Nicolas Graner
2020-09-05 13:51 ` Lars Ingebrigtsen
2020-09-05 17:18 ` Nicolas Graner
2020-09-05 23:59 ` Lars Ingebrigtsen
2020-09-06 1:55 ` Stefan Monnier
2020-09-06 11:48 ` Lars Ingebrigtsen
2020-09-06 12:29 ` Nicolas Graner
2020-09-06 12:35 ` Lars Ingebrigtsen [this message]
2020-09-06 14:40 ` Eli Zaretskii
2020-09-06 14:41 ` Lars Ingebrigtsen
2020-09-06 14:57 ` Eli Zaretskii
2020-09-06 17:05 ` Lars Ingebrigtsen
2020-09-06 17:56 ` Nicolas Graner
2020-09-06 19:32 ` Lars Ingebrigtsen
2020-09-06 17:06 ` Drew Adams
2020-09-06 17:12 ` Lars Ingebrigtsen
2020-09-06 17:18 ` Drew Adams
2020-09-06 17:26 ` Lars Ingebrigtsen
2020-09-06 18:57 ` Stefan Monnier
2020-09-06 22:49 ` Lars Ingebrigtsen
2020-09-06 22:56 ` Lars Ingebrigtsen
2020-09-06 4:41 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh63t75i.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43218@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas.graner@universite-paris-saclay.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).