Bug 767338 - Upward directed context menu's can appear under gnome-shell panel
Summary: Upward directed context menu's can appear under gnome-shell panel
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 20:36 UTC by Matt Reid
Modified: 2012-01-27 14:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-27 14:34:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
shows an Inkscape menu underneath the Shell on a 1080p display (30.94 KB, image/png)
2011-12-13 20:36 UTC, Matt Reid
no flags Details

Description Matt Reid 2011-12-13 20:36:13 UTC
Created attachment 546383 [details]
shows an Inkscape menu underneath the Shell on a 1080p display

Description of problem:
Large context menus can appear underneath the gnome-shell panel when they are directed upward. This seems to be more common with netbooks, but I can easily make this happen with inkscape on my 1080p display.

Version-Release number of selected component (if applicable):
gnome-shell-3.2.1-2.fc16.x86_64
3.1.4-1.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open Inkscape
2. Make a shape somewhere
3. Press Ctrl+Shift+F to open Fill and Stroke 
4. Change the dash style to something near the bottom of the list
5. Open up the dash style selector again, it now terminates underneath the gnome-shell panel
  
Actual results:
Can't select the top option in the dash style menu because it is underneath the shell

Expected results:
Menus should know that the space under the shell panel isn't usable and stop before they are obscured

Additional info:
There's an open bug on the GNOME BZ, but all activity has been "me too" - https://bugzilla.gnome.org/show_bug.cgi?id=660827

Comment 1 Matt Reid 2012-01-27 14:34:59 UTC
This has been fixed in git. I assume in F17 this won't be an issue anymore.


Note You need to log in before you can comment on or make changes to this bug.