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 548809 - New window not get focus if there is one window set to "always on top"
New window not get focus if there is one window set to "always on top"
Status: RESOLVED DUPLICATE of bug 534752
Product: metacity
Classification: Other
Component: Focus
trunk
Other All
: Normal normal
: ---
Assigned To: Thomas Thurman
Metacity maintainers list
: 577497 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-08-21 08:14 UTC by Chris Wang
Modified: 2009-03-31 17:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Chris Wang 2008-08-21 08:14:56 UTC
Please describe the problem:
When we set one window to "always on top", then set focus to another window (without setting "always on top") and create a new window from the second window, the focus will stay on the second window.

Steps to reproduce:
1.Open a terminal and put on the upper-right corner 
2.Open another terminal window using short-cut, the focus stay on the first window(which set to always on top). 
3.In the second window (without setting "always on top" but now focused) create a new window with short-cut.
4. The focus stay on the second window.

Actual results:


Expected results:
I didn't get into the logic yet, but I think when we create a window from the window which has set to be "always on top", we can expect the focus will not move the the other window, but in the second case, we create a new window from the window which not setting to "always on top" (but there is other window does), we should expect the new window get focus

Does this happen every time?
yes

Other information:
Can someone explain why we process the case in current way if you believe this is not a bug but a appropriate logic.
Comment 1 Marcel Telka 2009-02-18 16:52:51 UTC
I think this bug is duplicate of bug 534752. It could be closed.
Comment 2 Olav Vitters 2009-03-31 17:34:52 UTC
*** Bug 577497 has been marked as a duplicate of this bug. ***
Comment 3 Olav Vitters 2009-03-31 17:35:48 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 534752 ***