From: David Ponce via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 73911@debbugs.gnu.org
Subject: bug#73911: Issue with `widget-specify-button'
Date: Tue, 31 Dec 2024 17:12:27 +0100 [thread overview]
Message-ID: <b760e004-39c4-4601-9b2e-8c4cfc0a3636@orange.fr> (raw)
In-Reply-To: <7cc4a2df-41d7-4b11-8fe9-c4b639ed7c8e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
On 2024-12-31 12:34, Mauro Aranda wrote:
[...]
> >> > > > Mauro, any comments?
> >> > > >
> >> > > >
> >> > > >
>
> I don't really know the effects that this change could have (whether
> good or bad). The added invisible space comes from Bug#51550, which
> involved some discussions about the display engine itself.
>
> I had trouble reproducing the bug itself, since I don't understand what
> the unexpected result is.
>
> David, I'm sorry it took me so long to reply, but can you explain a bit
> more what's the unexpected result? Thank you.
>
Hi Mauro,
I attached a screenshot of the result:
1. with the current version of `widget-specify-button' which clearly shows
the unexpected appearance of the "OK" button when the button face has a
:box attribute and the button prefix use a display space property.
2. with the patched version of `widget-specify-button' which shows the
expected appearance of the same "OK" button.
It seems the problem is due to the invisible space inserted in front of the
button without specifying the face property, which causes a discontinuous
display of the button prefix when it uses a display space property.
I don't really know how to explain this better, sorry.
My proposed change just set the face of the invisible space to the button
face, which seems to fix the appearance of the button when the button
prefix has a display space text property.
I hope you will enjoy the new year.
Thank you for your help.
[-- Attachment #2: Screenshot.jpg --]
[-- Type: image/jpeg, Size: 69693 bytes --]
next prev parent reply other threads:[~2024-12-31 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 13:01 bug#73911: Issue with `widget-specify-button' David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-02 11:39 ` Eli Zaretskii
2024-11-16 13:44 ` Eli Zaretskii
2024-11-30 9:54 ` Eli Zaretskii
2024-12-14 9:35 ` Eli Zaretskii
2024-12-28 11:11 ` Eli Zaretskii
2024-12-31 11:34 ` Mauro Aranda
2024-12-31 13:34 ` Eli Zaretskii
2024-12-31 16:32 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-31 16:12 ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-01 11:03 ` Mauro Aranda
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b760e004-39c4-4601-9b2e-8c4cfc0a3636@orange.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=73911@debbugs.gnu.org \
--cc=da_vid@orange.fr \
--cc=eliz@gnu.org \
--cc=maurooaranda@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.