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 129158 - Window under pointer often left unfocused in sloppy/follow mode
Window under pointer often left unfocused in sloppy/follow mode
Status: RESOLVED DUPLICATE of bug 115072
Product: metacity
Classification: Other
Component: general
2.4.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2003-12-12 00:28 UTC by Tony Houghton
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description Tony Houghton 2003-12-12 00:28:58 UTC
There are a number of circumstances when the window under the pointer is
unfocused in sloppy or follow mode. I think in these modes the window under
the pointer should always have focus (except special unfocusable windows)
to avoid confusion. I've deliberately left the severity as "normal" because
I get too annoyed by typing into the wrong window to justify "trivial".

(a) When closing a window, focus is given to the window that was last
focused even if it is not the one now under the pointer.

(b) New windows grab focus even if you're still typing in another one. This
has been discussed in bugs 82921, 118372 and more, but while there are
valid arguments in favour focusing new windows, I don't think they should
apply in sloppy/follow modes.

(c) If there's a delay in switching workspaces due to swapping etc this
often results in Nautilus gaining focus instead of the window under the
pointer.
Comment 1 Rob Adams 2003-12-12 16:21:20 UTC

*** This bug has been marked as a duplicate of 115072 ***
Comment 2 Elijah Newren 2004-09-04 18:19:40 UTC
(a) and (c) are actually duplicates of 135810 (which has been fixed); (b) is
being implemented further in 118372, 149028 and so forth.

(I was just searching for a different old bug, saw this one, and thought I'd add
a little comment)