Launcher: auto-hide gets stuck sometimes / Nux don't sent enter/leave events
Bug #763275 reported by
Paul Sladen
This bug report is a duplicate of:
Bug #769703: Unity launcher does not auto hide when using dragging in Qt softwares.
Edit
Remove
This bug affects 14 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nux |
Fix Released
|
Medium
|
Unassigned | ||
Unity |
Fix Released
|
Medium
|
Unassigned | ||
nux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
To reproduce:
1. Starting in the centre of the screen
2. Slide pointer up to top-edge of screen
3. Slide pointer left to top-left corner pixel
4. Slide pointer down to left-edge of screen
5. Slide pointer right to centre of the screen
What happens:
Launcher gets stuck open
What should happen:
Launcher should autohide
This is a fairly frequent occurrence. As use-case that causes it is aiming for the browser back-button and overshooting in all directions, after which the browser back button (original target) is now covered and inaccessible!
description: | updated |
Changed in unity: | |
status: | New → Confirmed |
Changed in unity (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → ubuntu-11.10 |
milestone: | ubuntu-11.10 → ubuntu-11.04 |
summary: |
- Laucher: auto-hide gets stuck open if point arrives to left-edge via + Launcher: auto-hide gets stuck open if point arrives to left-edge via top-left pixel |
summary: |
- Launcher: auto-hide gets stuck open if point arrives to left-edge via + Launcher: auto-hide gets stuck open if pointer arrives to left-edge via top-left pixel |
Changed in unity: | |
assignee: | nobody → Didier Roche (didrocks) |
status: | Confirmed → Triaged |
importance: | Undecided → High |
milestone: | none → 3.8.10 |
Changed in unity: | |
milestone: | 3.8.10 → 3.8.12 |
Changed in unity: | |
status: | Triaged → Fix Released |
Changed in nux: | |
status: | Triaged → Fix Released |
Changed in unity: | |
milestone: | 3.8.12 → 3.8.10 |
To post a comment you must log in.
After talking to Paul, it's not 100% reproducible and seems to be related to missing nux events. We didn't have a bug for tracking it, let's take this one as a reference.