From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) BuildID: 2001040604 Right-click to bring up the context menu. Move the pointer over one of the items, like "Back" (doesn't matter if it's active or not). Right-click, and drag the pointer off the menu. Then release the mouse button while not pointing to the menu. Viola, the context-menu for frame pages! Reproducible: Always Steps to Reproduce: 1. Open a dull (frameless) page, like about:blank 2. Right-click to bring up the normal context menu (Back, Forward, etc.) 3. Right-click and hold the mouse button on one of the menu items, and drag the pointer off the menu. 4. Release the right mouse button with the pointer over some empty area off the menu. Actual Results: You'll see the context-menu for frame pages, i.e., "Open frame in new window", etc. It's a couple lines (20 pixels or so) below the pointer, too. Expected Results: Either display the correct (non-frame) context-menu again, or don't display any menu. If a menu is displayed, it should be directly under the current pointer position, not below it by 20 pixels. In the incorrect context-menu, - selecting "Open frame in new window" does nothing - selecting "Show only this frame" appears to open chrome://navigator/content/navigator.xul, thus giving the window a second menubar, toolbar, and status bar. Truly weird.

WORKSFORME with 2001041621 on Linux.

wierd

Seeing this on Win2000 with this morning's build. It also kills keyboard input, probably because the dismissal listener for the first context menu gets lost. Makes sense, kinda. Windows context menus appear on mouse up, so the listener catches the mouse up that occurs after dragging off and releasing the button. <guessing> The active "document" is a popup frame, so the frame-specific context menu appears. </guessing> Context menus on Linux appear on mouse down, so this isn't seen. -->pink

I tried this on 2001060504/Win2k just now, and it doesn't give the frame menu any more. So I guess it's partially fixed. It still kills keyboard input, though.

Reproduced with 2001122803/WinXP.

I posted bug 122302 for similar problem.

*** This bug has been marked as a duplicate of 122302 ***