Closed
Bug 297420
Opened 20 years ago
Closed 20 years ago
Bad positioning of context menu, when large, often partially off screen
Categories
(Firefox :: Menus, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 245163
People
(Reporter: vaclavjuza, Unassigned)
Details
Attachments
(2 files)
User-Agent: Opera/8.01 (X11; Linux i686; U; cs)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050325 Firefox/1.0.2 (Debian package 1.0.2-1)
The context menu is always positioned so, that its top border is at mouse
position, if it does not fit, the bottom border is there. If the menu is larger
or screen resolution smaller (menu higher than half of screen height) and mouse
is somewhere in the middle, higher part of context menu is off screen.
Reproducible: Always
Steps to Reproduce:
1.Install some extensions, that add fileds into context menu
2.Possibly decrease screen resolution (if enough extensions, 1024x768 is enough
).
3.Open a page or web gallery where there are images in hyperlinks (there are
usually many active context menu fileds)
4.Scroll such an element in the vertical middle of the screen.
5.Right-click on that element.
Actual Results:
Context menu has bottom border at the click-point, its upper part is dislpayed
partially off screen.
Expected Results:
the context menu should be displayed lower, so that it would be completely
visible.
I use 1024x768 resloution, extension adding to ctx menu: image zoomer, gcache,
adblock, remove-it-permanently, down-them-all, reload every, nuke anything, open
in this window.
(But the bug can be reprodiced using fewer extension. In my worst case,
9 fileds and 2 separators are hidden beyond screen border)
Very annoying when
Reporter | ||
Comment 1•20 years ago
|
||
Reporter | ||
Comment 2•20 years ago
|
||
Screenshots added
Comment 3•20 years ago
|
||
This has already been fixed, duping
*** This bug has been marked as a duplicate of 245163 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•