Closed Bug 292155 Opened 20 years ago Closed 20 years ago

Context menu is drawn off screen when using Windows shortcut key on a link

Categories

(Firefox :: Menus, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

()

RESOLVED DUPLICATE of bug 245163

People

(Reporter: babywafn, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

When using keyboard navigation (TAB, Space, Windows Menu Key) to navigate links,
pressing the Windows Menu Key to bring up the context menu for any links near
the bottom of the current viewport causes Firefox to draw the context menu
partly or completely off the bottom of the screen. 

Reproducible: Always

Steps to Reproduce:
1. Load a document with hyperlinks which is long enough to require scrolling
vertically.
2. Using keyboard navigation, place the system caret (highlight) over a link
near the bottom of the current viewport, with Firefox maximized to have its
edges up against the edge of your screen. 
3. Press the Windows Menu Key to bring up the context menu. 

Actual Results:  
The top left corner of the context menu is drawn at the top left corner of the
hyperlink's bounding box, which leads to the context menu being drawn off the
visible screen when the hyperlink is near the bottom edge of the screen.

Expected Results:  
The context menu's height and width need to be taken into account when drawing,
and if the menu height plus the menu's vertical location is greater than the
screen's height, then the context menu needs to be drawn at (link_location.y -
context_menu.height) or something similar, rather than drawing at link_location.y 

This bug occurred using the default theme and several different versions of
Firefox.
*** Bug 292157 has been marked as a duplicate of this bug. ***
Please always search before you file a bug, this one is very easy to find.


*** This bug has been marked as a duplicate of 245163 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.