Community
Participate
Working Groups
Build Identifier: I20100506-0800 If the Windows-7 taskbar is placed at the top of the screen (as opposed to the default bottom) context menus which are too tall and have their down arrow located off screen. (This is with a vertical resolution of 800) Reproducible: Always Steps to Reproduce: 1. Move the Windows-7 taskbar to the top of the screen, use a 2. Set the vertical resolution to ~800 3. Open a java file in Eclipse then right-click in the window
Created attachment 167805 [details] screenshot
Looks like a problem in Windos itself, the chevrons on top and on bottom of the menu are provided by the OS not SWT. do you have any other application in the system with big context menus ?
I haven't been able to find anything else with a context menu long enough to force chevrons (even if I were to drop resolutions.) Its definitely possible that its caused by Windows, despite allowing changing the taskbar position since Win95 Microsoft seem to let a lot of problems with it slide.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
The bug is alive. If I open "refactor" or "navigate" menu from the top on a Laptop with low pixel height (768px), i see the chevrons. If i open the context menu in the package explorer, the chevron is missed. Steps: Screen: 1366x768px, 12,5', Sans 13, Monospace 13 OS: Linux Eclipse: Version: 2019-09 R (4.13.0) Open Java Project, left click Navigate -> Chevron OK Right click somewhere in Package explorer subwindow -> Chevron missed, some menu points are out of the screen.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
