From: Nicolas Graner <nicolas.graner@universite-paris-saclay.fr>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43227@debbugs.gnu.org
Subject: bug#43227: EWW ignores 'multiple' attribute of 'select'
Date: Mon, 07 Sep 2020 10:51:02 +0200 [thread overview]
Message-ID: <86h7sat1ft.fsf@hypra-xx> (raw)
In-Reply-To: <87a6y2bj62.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 07 Sep 2020 01:05:25 +0200)
Lars Ingebrigtsen <larsi@gnus.org> wrote on 2020-09-07 01:05:
> In the context of the new drop-down menu...
>
> Perhaps they could just be rendered as
>
> [ ] Val1
> [ ] Val2
>
> and if you choose one of them, then we go to
>
> [x] Val1
> [ ] Val2
>
> (and close the menu), and then you have to open it again to click on:
>
> [x] Val1
> [x] Val2
This looks really awkward. Reopening the menu for each item you want to
select or deselect is inefficient and counter-intuitive. Besides, it
leaves open the question of how to render a multiple select in the eww
buffer, showing which options are selected.
> Because I don't know a way to make the menu stay up after clicking on it.
Pop-up menus are probably not the right tool to implement multiple
selects. There is a reason why graphical browsers offer quite different
interfaces to single and multiple selects.
I stand by my suggestion that a multiple select should look similar to a
list of checkboxes. Maybe it could actually be converted to checkboxes
at the DOM level, before rendering, and then let the normal checkbox
code do the job?
Nicolas
next prev parent reply other threads:[~2020-09-07 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 17:23 bug#43227: EWW ignores 'multiple' attribute of 'select' Nicolas Graner
2020-09-06 23:05 ` Lars Ingebrigtsen
2020-09-07 8:51 ` Nicolas Graner [this message]
2020-09-07 10:17 ` Lars Ingebrigtsen
2020-09-07 16:05 ` 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=86h7sat1ft.fsf@hypra-xx \
--to=nicolas.graner@universite-paris-saclay.fr \
--cc=43227@debbugs.gnu.org \
--cc=larsi@gnus.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.
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).