From: Eli Zaretskii <eliz@gnu.org>
To: Paul Nelson <ultrono@gmail.com>
Cc: 73037@debbugs.gnu.org
Subject: bug#73037: 31.0.50; fullscreen tooltips break after loading pdf-tools on MacOS
Date: Thu, 12 Sep 2024 12:16:38 +0300 [thread overview]
Message-ID: <86frq5kz9l.fsf@gnu.org> (raw)
In-Reply-To: <CAOA-32OKU4ZfNTLKQyRMPQ=DmJOKY8vGay7XWFLSZGWjnHAUaw@mail.gmail.com> (message from Paul Nelson on Thu, 5 Sep 2024 11:01:11 +0200)
> From: Paul Nelson <ultrono@gmail.com>
> Date: Thu, 5 Sep 2024 11:01:11 +0200
>
> I've tested the following setups:
>
> (1) Emacs master, pdf-tools 1.1.0
> (2) Emacs 29.4, pdf-tools 1.1.0
>
> The issue appears with (1) but not (2), so I figured I'd report it as
> a bug with Emacs rather than pdf-tools, but would welcome other
> suggestions.
>
> Steps to reproduce:
>
> 1. Install pdf-tools (e.g., via list-packages)
>
> 2. Emacs -Q
>
> 3. Evaluate the following:
>
> (package-initialize)
> (use-package pdf-tools
> :config
> (pdf-tools-install :no-query))
>
> 4. Visit any pdf file.
>
> These steps put Emacs in a state where tooltips behave badly: when the
> current frame is fullscreen (via (toggle-frame-fullscreen)), tooltips
> display in a separate fullscreen frame rather than as a child frame.
>
> All tooltips are affected, not just those produced by pdf-tools. For
> example, (x-show-tip "This is a tooltip." (selected-frame) nil 5)
> triggers the issue, as does mousing over any link in *Help*.
Could you please report this to the developers of pdf-tools first, and
ask them to look into the issue? If they identify some issue with
core Emacs functionality, please then come back here with the details,
or ask them to post those details.
Thanks.
next prev parent reply other threads:[~2024-09-12 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 9:01 bug#73037: 31.0.50; fullscreen tooltips break after loading pdf-tools on MacOS Paul Nelson
2024-09-12 9:16 ` Eli Zaretskii [this message]
2024-09-12 9:31 ` Paul Nelson
2024-09-18 13:50 ` Paul Nelson
2024-09-18 15:50 ` Eli Zaretskii
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=86frq5kz9l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73037@debbugs.gnu.org \
--cc=ultrono@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.