[regression] Clicking on unity's panel does not raise a maximized window
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
With one maximized window below an unmaximized window, clicking on the Unity panel (with the maximized window focused) does not raise the maximized window. This happens with both focus-follows-mouse and focus-follows-
Steps to reproduce (with focus follows mouse):
1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B).
2. Raise window B so that B is in front of A.
3. Move mouse over window A to focus it.
4. Move mouse up to the unity panel while keeping window A focused.
5. Click on an empty space in the panel.
Observed behaviour: window A is not raised to the top, but it should. This used to work in Ubuntu 13.10, and 13.04, iirc.
This bug also occurs with focus-follows-
Steps to reproduce (with focus follows click):
1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B).
2. Raise window B so that B is in front of A.
3. Alt+RightClick on window B to bring up the window's context menu and enable the "Always on top" option.
4. Click on window A to focus it. Window B should remain in front of window A.
5. Alt+RightClick on window B to bring up the window's context menu, and disable the "Always on top" option. Window A should remain focused after this action.
6. Click on an empty space in the panel.
Observed behaviour: Window A is not raised to the top, but it should. I'm not sure if this worked in previous releases.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.
Uname: Linux 3.13.4-hyper1 x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins: [core,composite
CurrentDesktop: Unity
Date: Wed Mar 5 10:36:21 2014
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-03-03 (1 days ago)
Changed in unity: | |
status: | New → Fix Released |
This seems fixed in current trusty.