From: Lars Ingebrigtsen <larsi@gnus.org>
To: ynyaaa@gmail.com
Cc: 39115@debbugs.gnu.org
Subject: bug#39115: 26.3; eww consecutive links look like one link with mouse-over
Date: Wed, 22 Jan 2020 16:16:05 +0100 [thread overview]
Message-ID: <87sgk7ttca.fsf@gnus.org> (raw)
In-Reply-To: <86imlfxu7t.fsf@gmail.com> (ynyaaa@gmail.com's message of "Tue, 14 Jan 2020 00:16:22 +0900")
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
ynyaaa@gmail.com writes:
> If two or more links are consecutive without any blank characters,
> pointing one of them with mouse activates 'mouse-face of them all at
> the same time.
Here's a file that demonstrates the problem (open with `M-x eww-open-file'):
[-- Attachment #2: link.html --]
[-- Type: text/html, Size: 68 bytes --]
[-- Attachment #3: Type: text/plain, Size: 291 bytes --]
I don't know how to fix it, though. Is there a way to make two
consecutive mouse-face regions not light up at the same time when the
mouse pointer is over a part of one of the regions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-01-22 15:16 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 [this message]
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
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=87sgk7ttca.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39115@debbugs.gnu.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).