unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: john muhl via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Yuuki Harano <masm+emacs@masm11.me>
Cc: 48069@debbugs.gnu.org
Subject: bug#48069: 28.0.50; [feature/pgtk]; tooltips are jittery and sometimes obscured
Date: Mon, 03 May 2021 12:47:19 -0500	[thread overview]
Message-ID: <50edbb7c0d8570e67004b1bd0f7af0f059517881.camel@johnmuhl.mx> (raw)
In-Reply-To: <20210504.014655.1418467595728197173.masm@luna.pink.masm11.me>

On Tue, 2021-05-04 at 01:46 +0900, Yuuki Harano wrote:
> > In the menu-bar they appear behind the menu itself and obscure the
> > hint in the tooltip.
> 
> I'll debug it.

I wonder if these tooltips are even needed; they mostly just restate
what the item under point already says. I browsed around a few of the
default GNOME apps (and a few non-default others) but could not find
any that display tooltips when hovering an item in a drop down menu
the way Emacs does.

Would just getting rid of them be an alternative to debugging the
visibility issue?






  parent reply	other threads:[~2021-05-03 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 17:32 bug#48069: 28.0.50; [feature/pgtk]; tooltips are jittery and sometimes obscured john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-03 16:46 ` Yuuki Harano
2021-05-03 17:16   ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-03 17:47   ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-05-04  7:23     ` Yuuki Harano
2021-05-04 11:54       ` Eli Zaretskii
2021-05-04 12:50         ` Yuuki Harano
2021-05-04 13:00           ` Eli Zaretskii
2021-05-08 15:57     ` Yuuki Harano
2021-05-12 15:48       ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-13 15:20         ` Yuuki Harano
2021-05-03 19:33   ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=50edbb7c0d8570e67004b1bd0f7af0f059517881.camel@johnmuhl.mx \
    --to=bug-gnu-emacs@gnu.org \
    --cc=48069@debbugs.gnu.org \
    --cc=email@johnmuhl.mx \
    --cc=masm+emacs@masm11.me \
    /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).