Closed
Bug 51533
Opened 24 years ago
Closed 24 years ago
Menus don't stay visible
Categories
(Core :: XUL, defect, P3)
Tracking
()
Future
People
(Reporter: hrunting, Assigned: mikepinkerton)
Details
Under Win32 systems, when you click on a menu, the menu /should/ stay open, as
is the case with the rest of Windows menus. With the new M18 nightlies, you
have to click and hold and drag to the menu item that you want. This has the
unfortunate effect of completely disabling the right-click menu because when you
right-click and then move your mouse over the menu, the menu disappears, if you
hold the right-click button, you can't select anything.
Return Menus to their previous defaults. When you click on a menu, it should
stay open, not require you to continue holding the click (actually, what needs
to happen is that the menus should default to the behavior of the operating
system, ie. under Windows, you click, move, and click again to select. Under
Mac, you click/hold and then drag/release).
Comment 1•24 years ago
|
||
Menus _do_ stay up after the initial click. Worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•24 years ago
|
||
I figured out what the problem is. The system I am on has XMouse abilities
turned on in the system config. When this is turned off, the problem doesn't
exhibit itself. Presumably, this is because of how you've implemented your
menu code, implementing it as something other than what Windows thinks is a
menu. Is there a way you folks can fix /that/?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 3•24 years ago
|
||
no time to consider this in the current release, ->future
Target Milestone: --- → Future
Comment 4•24 years ago
|
||
Ah, that would be a duplicate ...
*** This bug has been marked as a duplicate of 50798 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•