Windows should not automatically be focused when opened if the focus is on another application
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Design |
Fix Released
|
Undecided
|
Unassigned | ||
Compiz Core |
Fix Released
|
Critical
|
Sam Spilsbury | ||
Unity |
Fix Released
|
Critical
|
Sam Spilsbury | ||
compiz (Ubuntu) |
Fix Released
|
Undecided
|
Sam Spilsbury | ||
Oneiric |
Fix Released
|
Undecided
|
Sam Spilsbury | ||
unity (Ubuntu) |
Fix Released
|
High
|
Sam Spilsbury | ||
Oneiric |
Fix Released
|
High
|
Sam Spilsbury |
Bug Description
If this is not a bug, or not a unity bug, please delete this bug report.
There are times when I press alt +F2 to start an application and it takes a while to start. Meanwhile, I am typing something in the other application I have open, and when the app I started finally loads it "cuts me off" from typing as it focuses on the new application. A solution to this would be to start new windows, if they are not dialogue boxes that is, in the background automatically if another window is focused or if one is typing.
EDIT: smspillaz: sorry to hijack this bug. I get the impression here that the focus stealing prevention behavior is correct, however the real issue at hand is that windows that are denied focus
are stacked on top, and then you can't raise the actual focused window to the top until you focus the window that was denied focus. I'll fix that.
TESTCASE
Make something crash or something
Apport should come up underneath the window you are currently working with
Related branches
- Jason Smith (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedsrc/window.cpp (+1/-1)
Changed in compiz-core: | |
importance: | High → Critical |
Changed in unity: | |
importance: | High → Critical |
Changed in unity: | |
milestone: | 4.6.0 → 4.8.0 |
Changed in compiz-core: | |
milestone: | none → 0.9.5.96 |
Changed in unity: | |
milestone: | 4.8.0 → 4.16.0 |
Changed in unity: | |
milestone: | 4.16.0 → 4.18.0 |
Changed in unity: | |
milestone: | 4.18.0 → 4.20.0 |
Changed in unity: | |
milestone: | 4.20.0 → 4.22.0 |
Changed in unity: | |
milestone: | 4.22.0 → 4.24.0 |
description: | updated |
Changed in ayatana-design: | |
status: | New → Fix Committed |
Changed in compiz-core: | |
status: | In Progress → Fix Committed |
Changed in unity: | |
status: | In Progress → Fix Committed |
Changed in unity (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in compiz (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Sam Spilsbury (smspillaz) |
Changed in unity (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in unity (Ubuntu Oneiric): | |
status: | Fix Released → Invalid |
description: | updated |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in compiz-core: | |
status: | Fix Committed → Fix Released |
Changed in compiz (Ubuntu): | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in unity (Ubuntu): | |
status: | Invalid → Fix Released |
Changed in unity (Ubuntu Oneiric): | |
status: | Invalid → Fix Released |
Changed in ayatana-design: | |
status: | Fix Committed → Fix Released |
Changed in compiz-core: | |
milestone: | 0.9.5.96 → 0.9.7.0 |
I don't think this would be a proper way to fix this problem. Imagine these user cases:
1) No windows are open, press Alt+F2 and open an application. If the application is, say, a web browser, and if it doesn't get focus, then the user would not be able to simply start typing to enter text in the address bar. He/she'd have to click the address bar once.
2) If its a small application which loads up quickly e.g. gedit, then it would be frustrating for the user to first start it from Alt+F2, and then click it again in the launcher, and then begin typing.
There can be many more such user cases which would be affected by such a change. Feel free to continue the discussion here on this bug. In the meantime I've marked it 'Opinion'.