Closed Bug 14476 Opened 21 years ago Closed 20 years ago
Context menus pop up in wrong location
Right mouse clicking in the content area causes the context menu to appear in the wrong location. It appears to be off by the offset of the content area from the upper-left corner of the overall window. It is easier to see than to explain; try it (I just checked in the change to navigator.xul to get the context menu wired to the content area).
reassigning to saari as p3 for m12
Verified on MacOS 1999-10-18 build (so OSes changed to `All'). For example, the standard page context menu begins: Back, Forward, Reload, Stop ... With navigation toolbar and personal toolbar visible, a context menu appears with `Stop' under the mouse pointer. With the toolbars collapsed, the context menu appears further down -- with `Back' under the mouse pointer. Correct behaviour would be for the top-left corner of the *first item* in the context menu to appear about 1~2 pixels south-east of the mouse pointer -- so if I accidentally click the right mouse button, I don't inadvertently select a context menu item.
mass-moving all m12 bugs to m13
[Contextual menu bug --- QA Assigning to self.]
http://lxr.mozilla.org/seamonkey/source/xpfe/browser/resources/content/nsContext Menu.js is this the file that needs to be fixed?
No, that's the code that manages the context menu content. The menu itself is displayed by underlying XUL stuff (mozilla/layout/xul/base/src/*.cpp) or even lower-level layout or widget code).
pavlov and myself are working on menupositioning in nsMenuPopupFrame.cpp right now.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
this appears fixed in the 12/01/99 build. I'm marking fixed, anyone object?
I'm unable to reproduce this using ordinary pages on this morning's Win32/Mac OS builds. Since the bug report lacks specific steps to reproduce, and Pavlov thinks its fixed (and can't reproduce on Linux), I'm rubber-stamping it as Verified-Fixed. If anyone is still seeing this, please re-open with your comments.
You need to log in before you can comment on or make changes to this bug.