From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nicolas Graner <nicolas.graner@universite-paris-saclay.fr>
Cc: 43218@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#43218: EWW handles default answer incorrectly when changing a select
Date: Sun, 06 Sep 2020 01:59:28 +0200 [thread overview]
Message-ID: <878sdn22sf.fsf@gnus.org> (raw)
In-Reply-To: <86ft7wuoq0.fsf@hypra-xx> (Nicolas Graner's message of "Sat, 05 Sep 2020 19:18:15 +0200")
Nicolas Graner <nicolas.graner@universite-paris-saclay.fr> writes:
> Activate the select and change its value to 'two'.
> Activate it again and answer <RET> to the prompt for value: the
> displayed value returns to 'one'.
>
> This is not critical as this situation is rare and the value sent to the
> server will be correct anyway, but it is confusing to the user who does
> not usually know the value of each option.
That's true... there's also a general problem with how the values are
selected: We're doing a completing-read over the display names, and then
mapping that back to the values. But this is perfectly valid:
<select name="a">
<option value="1">one</option>
<option value="2">one</option>
</select>
But there's no way to select the second value in eww.
Unfortunately, the Emacs primitives for prompting are very
text-oriented, and don't allow putting properties on the values we're
completing over, not even with:
---
minibuffer-allow-text-properties is a variable defined in ‘src/minibuf.c’.
Its value is nil
Probably introduced at or before Emacs version 20.
Documentation:
Non-nil means ‘read-from-minibuffer’ should not discard text properties.
This also affects ‘read-string’, but it does not affect ‘read-minibuffer’,
‘read-no-blanks-input’, or any of the functions that do minibuffer input
with completion; they always discard text properties.
---
I wonder what the logic behind this is? And I also have a vague feeling
I've asked this before...
Perhaps Stefan knows and or remembers. :-)
So the test case is:
(let ((minibuffer-allow-text-properties t))
(completing-read "Foo: " (list (propertize "foo" 'data 'bar))
nil 'require-match))
=> "foo"
instead of #("foo" 0 3 (data bar))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-05 23:59 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 [this message]
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
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=878sdn22sf.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).