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 318550 - skip_taskbar_hint interfers with tooltips
skip_taskbar_hint interfers with tooltips
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.8.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-10-11 08:44 UTC by Steffen Gutmann
Modified: 2018-02-10 03:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Exploit for reproducing the bug (973 bytes, text/plain)
2005-10-11 08:47 UTC, Steffen Gutmann 		Details

Description Steffen Gutmann 2005-10-11 08:44:33 UTC 
Version details: Runtime: gtk+-2.6
Distribution/Version: XP

1. compile and run the attached exploit.
2. move window 2 such that it is in front of and overlaps with window 1.
3. move the mouse pointer over the "Wait for my tooltip" label and wait until
the tooltips window appears.

On my system, this changes the stacking order of the windows such that window 2
is now behind window 1.

When commenting out the line 
    gtk_window_set_skip_taskbar_hint(GTK_WINDOW(window1), TRUE);
it works without problems.

Does not happen on Linux/X11.
Comment 1 Steffen Gutmann 2005-10-11 08:47:25 UTC 
Created attachment 53321 [details]
Exploit for reproducing the bug
Comment 2 Tor Lillqvist 2005-10-12 22:10:39 UTC 
Thanks for reporting this, and especially thanks for attaching a sample program.
The problem still exists in the current stable branch, 2.8.
Comment 3 Hiroyuki Yamamoto 2006-11-07 02:57:18 UTC 
In 2.10.x, removing gtk_window_set_skip_taskbar_hint() no longer help.
Probably because gtk_window_set_skip_taskbar_hint() is called somewhere inside GTK+.
Comment 4 Matthias Clasen 2018-02-10 03:46:00 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.