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 682431 - Dropbox context menu doesn't work with new tray
Dropbox context menu doesn't work with new tray
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: message-tray
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-08-22 08:00 UTC by Alexander Larsson
Modified: 2015-03-07 05:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Larsson 2012-08-22 08:00:02 UTC
The new notification tray has several problems with the dropbox notification icon right-click context menu:

1) If i open the tray by super-M or hot-corner then right-clicking on the dropbox icon does nothing.

2) In the overview, right-clicking on the icon exits overview mode and shows a menu. However, the placement of the menu is wrong, causing it to not be tall enough, forcing scrolling. It seems to me like it got the coordinates for the click being below the screen (just guessing).

3) If I open a notification using "zenity --notification --text=blah" and then mouse to the bubble and then to the corner to open the tray, then right-clicking on the dropbox icon *does* show the menu. However, it is positioned wrong in a different way. The menu has the full height, but it is placed one tray-height above the tray. The mouse input is in the "correct" place causing the highlighted menu item to be one tray-height above the mouse cursor.

4) Less problematic, but the context menu once visible is in the dimmed out layer with the other non-tray windows. It would be nice if any windows that have parents in the tray were not dimmed out.
Comment 1 Alexander Larsson 2012-08-22 08:06:44 UTC
Also, while playing around with this I twice got an exception that made me have to restart the shell, see bug 682433.
Comment 2 Alexander Larsson 2012-08-22 10:16:40 UTC
This seems like a partial dup of bug 682244
Comment 3 Florian Müllner 2015-03-07 05:54:48 UTC
This has been fixed in 3.16.