Closed Bug 55764 Opened 26 years ago Closed 25 years ago

Right-click on button part of menubutton should open menu

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 45961
Milestone:
Future

People

(Reporter: ezh, Assigned: trudelle)

Details

Now I must click on the small triangle (what is very hard on 1280*1024 coz it's so small) what is on the bottom of Back/Forward buttons. I wish it works like in NN 4.x - right click on the Back/Forward button activates it.
We used to have a click and hold option as well but this does not exist either. It would be nice if they were both supported but nothing like this made it in for this version.
Status: NEW → ASSIGNED
That comment doesn't make sense, since (a) it has been well and truly decided (several times) by the XPToolkit/Widgets people that click-and-hold will not be supported for menubuttons for usability reasons, and (b) it's going to be several months until `this version' is released. --> XPToolkit/Widgets.
Assignee: hangas → trudelle
Status: ASSIGNED → NEW
Component: User Interface: Design Feedback → XP Toolkit/Widgets
OS: other → All
QA Contact: mpt → jrgm
Hardware: PC → All
Summary: Pressing rihgt mouse button get the listing of previous visited pages → Right-click on button part of menubutton should open menu
Right-click on a menu sounds pretty un-discoverable to me. Have we ever seen anyone try it in a usability test? If we did it, would anyone ever find it? ->future
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Keywords: 4xp
Back and Forward buttons in navigator have a context menu (i.e. right-click opens the menupopup) but I had to look at the code (!) to know that it even existed. It's quite unnatural. I'm not sure this would be such a good thing really. Fabian.
Internet Explorer does this too, overriding the normal right mouse button behavior in the toolbar (opening the Toolbars context menu).
I'm sure I saw this working in the build I downloaded earlier today at work. Marking fixed and leaving for someone to verify.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
If you didn't fix a bug yourself (or get notified by the person who fixed it), you may mark a bug as WORKSFORME, but not as FIXED. And if you mark a bug WORKSFORME you should note the build id and platform. Reopening.
Status: RESOLVED → REOPENED
Keywords: qawanted
Resolution: FIXED → ---
Why be so pedantic? Someone obviously fixed this. Resolving as wfm in build id 0000000000000 (a recent personal build, and no, I didn't count the number of zeroes) on Win98.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Shoot me.
[I fixed this per bug 45961...verifying wfm anyways]
Status: RESOLVED → VERIFIED
So really this is a dupe of 45961...
! marking dup of 45961 to make everybody happy.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
DUP OF 45961. *** This bug has been marked as a duplicate of 45961 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
VERIFIED.
Status: RESOLVED → VERIFIED
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.