After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686394 - Incorrect positioning of tooltips on vertical toolbars when going from one button to another
Incorrect positioning of tooltips on vertical toolbars when going from one bu...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkToolbar
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 682886
 
 
Reported: 2012-10-18 16:34 UTC by Jean-François Fortin Tam
Modified: 2018-04-15 00:38 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screencast (633.26 KB, video/webm)
2012-10-18 16:34 UTC, Jean-François Fortin Tam 		Details

Description Jean-François Fortin Tam 2012-10-18 16:34:08 UTC 
Created attachment 226751 [details]
screencast

When moving from one button to another (instead of making the mouse exit and re-enter the toolbar), the tooltip positioning is incorrect and varies depending on the direction you're going in (upwards or downwards), often being cut off from the screen (and thus unreadable).

This only happens on vertical toolbars. In this particular case, it was using the inline-toolbar style.
Comment 1 Cosimo Cecchi 2013-08-04 22:15:18 UTC 
This also seems to happen with Nautilus when the window is right-edge snapped. After investigating it for a while, it seems the positioning code for the "browse mode" is wrong when the tooltip is about to be positioned close to the right edge of the screen.
Comment 2 Jean-François Fortin Tam 2015-06-23 03:21:58 UTC 
Still occurs to this day...
Comment 3 Matthias Clasen 2018-02-10 05:26:52 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Matthias Clasen 2018-04-15 00:38:19 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new