menu mouse-scrolling broken, when themes enable gtk-auto-mnemonics
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Ubuntu |
In Progress
|
Medium
|
Cody Russell | ||
GTK+ |
Fix Released
|
Medium
|
|||
Fedora |
Won't Fix
|
Medium
|
|||
gtk+2.0 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Lucid |
Won't Fix
|
Medium
|
Unassigned | ||
gtk+3.0 (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Lucid |
Invalid
|
Low
|
Unassigned |
Bug Description
This bug is a follow-up to bug #537374. The keyboard aspect of that bug is now fixed, but the mouse-handling problem remains.
How to reproduce:
0.1) Make sure you are testing on a display that has a sufficiently low resolution to make the System -> Preferences menu too high to fit on the screen.
0.2) Make sure you are using a theme that uses the : gtk-auto-mnemonics = 1 option (e.g., Ambiance or Radiance).
1) Bring up the System -> Preferences menu.
2) Place the mouse pointer on the down arrow.
3) Wait for the menu to scroll to the bottom.
4) Move the mouse pointer slightly upwards, aiming for the menu's bottom-most item.
Expected behavior: The menu should stay in its scrolled position, making it possible to click the bottom-most item.
Actual behavior: As soon as the mouse pointer leaves the down arrow, the menu scrolls back to the top. It is not possible to click the bottom-most item.
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: c2d78d7690d0fab
CheckboxSystem: 90b928d283473e9
Date: Fri Mar 26 10:08:46 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelMo
Package: light-themes 0.1.5.9
PackageArchitec
ProcVersionSign
SourcePackage: light-themes
Uname: Linux 2.6.32-17-generic x86_64
Related branches
Changed in gtk+2.0 (Ubuntu): | |
assignee: | nobody → Canonical Desktop Team (canonical-desktop-team) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in ayatana-ubuntu: | |
assignee: | nobody → Cody Russell (bratsche) |
importance: | Undecided → Medium |
milestone: | none → ubuntu-10.04-beta-2 |
status: | New → Triaged |
Changed in ayatana-ubuntu: | |
milestone: | ubuntu-10.04-beta-2 → ubuntu-10.04 |
Changed in ayatana-ubuntu: | |
status: | Triaged → In Progress |
Changed in gtk+2.0 (Ubuntu Lucid): | |
status: | Triaged → In Progress |
Changed in gtk+2.0 (Ubuntu Lucid): | |
milestone: | none → lucid-updates |
Changed in gtk: | |
status: | Unknown → Confirmed |
Changed in gtk+2.0 (Ubuntu): | |
milestone: | lucid-updates → none |
assignee: | Canonical Desktop Team (canonical-desktop-team) → nobody |
Changed in gtk+2.0 (Ubuntu Lucid): | |
assignee: | Canonical Desktop Team (canonical-desktop-team) → nobody |
Changed in gtk: | |
importance: | Unknown → Medium |
Changed in gtk: | |
status: | Confirmed → Fix Released |
Changed in gtk+2.0 (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in fedora: | |
importance: | Unknown → Medium |
status: | Unknown → Won't Fix |
I would like to see this fix, but do not consider this a release blocker. Downgrading to medium.