From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 39115@debbugs.gnu.org, ynyaaa@gmail.com
Subject: bug#39115: 26.3; eww consecutive links look like one link with mouse-over
Date: Wed, 22 Jan 2020 21:44:11 +0100 [thread overview]
Message-ID: <87y2tzp6g4.fsf@gmx.net> (raw)
In-Reply-To: <83r1zrthvn.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 Jan 2020 21:23:40 +0200")
On Wed, 22 Jan 2020 21:23:40 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: Lars Ingebrigtsen <larsi@gnus.org>, ynyaaa@gmail.com,
>> 39115@debbugs.gnu.org
>> Date: Wed, 22 Jan 2020 20:15:10 +0100
>>
>> > Not without changes to C-level code, no. It currently traverses the
>> > glyphs looking for the first one that doesn't have the mouse-face, so
>> > if two stretches of text one after the other have that face, it won't
>> > notice.
>>
>> That appears to be so only if the respective face values of the
>> mouse-face properties have the same name; if the face names are
>> different, even if one inherits from the other so they are visually
>> indistinguishable, then each propertized string gets highlighted
>> independently when the mouse pointer hovers over it
>
> That goes without saying, but I thought the request was for the
> "normal" mouse face to be able to do that. It sounds a kludge to me
> to ask that each button uses a different value of mouse-face, since it
> means someone should construct each button by hand, and not generate
> them by generic code.
I also think it would only be worth considering if it could be
programmed. But for buttons, it seems the problem does not arise: I
just checked insert-button, and it uses overlays, which appear not to
have the adjacency issue that text properties have:
(progn
(insert-button "one" 'mouse-face 'highlight)
(insert-button "two" 'mouse-face 'highlight)
(insert-button "three" 'mouse-face 'highlight))
Why do overlays and text properties differ on this?
Steve Berman
next prev parent reply other threads:[~2020-01-22 20:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 15:16 bug#39115: 26.3; eww consecutive links look like one link with mouse-over ynyaaa
2020-01-22 15:16 ` Lars Ingebrigtsen
2020-01-22 15:27 ` Robert Pluim
2020-01-22 15:29 ` Lars Ingebrigtsen
2020-01-22 15:40 ` Robert Pluim
2020-01-22 15:45 ` Lars Ingebrigtsen
2020-01-22 16:05 ` Robert Pluim
2020-01-22 16:31 ` Eli Zaretskii
2020-01-22 19:15 ` Stephen Berman
2020-01-22 19:23 ` Eli Zaretskii
2020-01-22 20:44 ` Stephen Berman [this message]
2020-01-23 12:22 ` Lars Ingebrigtsen
2020-01-23 14:47 ` Stephen Berman
2020-01-23 14:39 ` Eli Zaretskii
2020-01-23 12:16 ` Lars Ingebrigtsen
2020-01-23 1:47 ` ynyaaa
2020-01-23 12:18 ` Lars Ingebrigtsen
2020-01-23 14:28 ` Eli Zaretskii
2020-01-24 15:24 ` Lars Ingebrigtsen
2020-01-24 15:41 ` Eli Zaretskii
2020-02-19 13:09 ` Lars Ingebrigtsen
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=87y2tzp6g4.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=39115@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=ynyaaa@gmail.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.
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).