GNOME Bugzilla – Bug 155450
TRACKER: Focus related bugs
Last modified: 2020-11-06 20:06:30 UTC
This bug will be here to track focus related bugs. I'll add dependencies for the following in a minute: 88194 metacity forgets which window had focus after restart 90382 Some kind of meta bug about focus tracking in general 100470 panel gets focus when it shouldn't 107347 app doesn't focus on map when it moves itself after showing 123366 visual bell modifies focus window 123576 alt+esc+any leaves raised unfocused window on top (may be raise issue) 126489 refuse to focus a window with a modal transient (& other stuff; 152283) 140977 Double focus due to WM_TAKE_FOCUS 143147 alt-tab freeze just after login (might be uninitialized-mrulist though) 149028 focus-stealing-bugs tracker 152004 strict pointer mode (i.e. focus on map iff window is under pointer) 154598 Alter meaning of expected_focus_window ?????? Windows can be multiply focused (see comment 2 of 140977; also 154598)
*** Bug 166732 has been marked as a duplicate of this bug. ***
(166732 was not a dupe--it was a botched attempt at marking it as blocking this bug...)
Adding evolution bug here as I'm not aware of desktop-wide focus bug tracker. 273912 Compose window not presented when launched from another application (focus stealing prevention)
Tommi: focus stealing prevention bugs do not belong in this tracker; they belong in bug 149028. (Most focus stealing prevention bugs are bugs in applications or in gtk+; while I like having a tracker for them, there's so many that I want them in a separate bug just for organization sake--however, this bug depends on 149028, meaning that it depends on all bugs that 149028 does)
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.