After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728334 - Open attachment drop-down usability issue
Open attachment drop-down usability issue
Status: RESOLVED DUPLICATE of bug 591258
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-04-16 11:57 UTC by Tobias Getzner
Modified: 2015-03-09 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The drop-down button was where "open with gedit" is shown; releasing the button unintentionally opens the attachment in gedit. (22.84 KB, image/png)
2014-04-16 11:57 UTC, Tobias Getzner
Details

Description Tobias Getzner 2014-04-16 11:57:16 UTC
Created attachment 274454 [details]
The drop-down button was where "open with gedit" is shown; releasing the button unintentionally opens the attachment in gedit.

The „open attachment“ drop-down menu has usability issues when it’s located near the bottom of the screen (i.e. when there’s not enough space to the bottom to show the menu). Under these circumstances, the menu will be shown on top of the button, and releasing the click will count as selection. So if you release the button (expecting that the menu will stay open) you unintentionally trigger a menu item. Additionally, the dropdown menu will be too small too display all entries and require scrolling.

It would be better if the menu opened to the top when there’s insufficient space to the bottom, and it should never be rendered on top of the button used to open the menu. If it can only be rendered on top of the button, then releasing the button should not immediately trigger the menu selection.
Comment 1 Milan Crha 2015-03-09 15:06:44 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 591258 ***