Dashboard interaction error
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
New
|
Undecided
|
Unassigned | ||
| Unity |
Incomplete
|
Undecided
|
Unassigned | ||
| unity (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
Dear colleague developers,
I know that what I am about to file might not be considered to be a bug by many. It's actually somewhere between the bugs and feature ideas areas, maybe not a bug at all for some of you. Though, I have decided to file it here since I think that what I am about to describe is cognitively incorrect in the HCI field.
If you see the attachment, my mouse cursor is in the middle of two icons. The space between them is significantly large, though an application is highlighted at all times. In this particular example the one on the left is highlighted and if I click on the middle of this void space the left hand side application will be launched of course. This is exactly what I would describe as cognitively incorrect. An icon should be highlighted when the mouse cursor is exactly over it. The current implementation also increases the probability of accidental application launches which could leave the user wondering...
At the same time I would like to propose that this void space could be used as follows. I could click on it, keep the mouse button pressed, move the mouse and thus have an alternative and easy way of scrolling through the dashboard's contents. This combines well with the particularly small white scrollbar of the dashboard and the other bug I have filed :-).
Thank you.
| cg (chr1st0scli) wrote | #1 |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #2 |
| tags: | added: bot-comment |
| affects: | ubuntu → unity (Ubuntu) |
| Omer Akram (om26er) wrote | #3 |
| Changed in unity: | |
| status: | New → Incomplete |
| Changed in unity (Ubuntu): | |
| status: | New → Incomplete |
| Omer Akram (om26er) wrote | #4 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/
To change the source package that this bug is filed about visit https:/
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]