When dragging slider, other menu items can mistakenly be activated on mouseup
Bug #538493 reported by
Matthew Paul Thomas
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Indicator Display Objects |
Triaged
|
Low
|
Unassigned | ||
| The Sound Menu |
Invalid
|
Low
|
Conor Curran | ||
| indicator-sound (Ubuntu) |
Invalid
|
Medium
|
Conor Curran | ||
Bug Description
Binary package hint: indicator-sound
indicator-sound 0.1.3.1-0ubuntu1, Ubuntu Lucid
1. Open the sound menu.
2. Start dragging the volume slider.
3. While dragging it, move the pointer over the "Mute All" item.
4. Release the button.
What happens:
3. The "Mute All" item highlights.
4. The "Mute All" item is activated, and the sound mutes.
What should happen:
3. The "Mute All" item does not highlight, because you're manipulating a different item.
4. Nothing.
| Changed in indicator-sound (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in indicator-sound (Ubuntu): | |
| assignee: | nobody → Conor Curran (cjcurran) |
| Changed in indicator-sound (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in indicator-sound: | |
| assignee: | nobody → Conor Curran (cjcurran) |
Revision history for this message
| Cody Russell (bratsche) wrote | #1 |
| Changed in indicator-sound: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in indicator-sound: | |
| status: | Confirmed → Invalid |
| Changed in indicator-sound (Ubuntu): | |
| status: | Triaged → Invalid |
| Changed in ido: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
This is actually in libido, not in indicator-sound. It's also probably not going to be an obvious one to fix. The problem is that we do some rather janky things in libido to work around the gtk grab system. The slider widget adds a grab when you mouse-down on the slider, but this also forces the menu to close which is why we work around it.
We can look into adding more janky solutions, like trying to see if it's possible to stop the button release event on other menuitems in the menu.
Another solution might be to create a GtkMenu derivative which doesn't close when a grab is added. I don't know off the top of my head what other side-effects we may have from this though. It could turn out to be more gross going that direction.