Closed Bug 170501 Opened 23 years ago Closed 23 years ago

Context menu doesn't appear when right clicking on disabled forward or back

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: j.moz, Assigned: hyatt)

References

Details

I noticed that right clicking on the toolbar brings up a context menu. Right clicking on an active back or forward arrow brings up back or forward history, which is fine, I guess. However, forward is almost always disabled in normal usage so right clicking on disabled forward (or disabled back) should bring up the context menu as well. Currently it does nothing. Right clicking on disabled Stop activates the menu, which is good.
Ack. Just in case someone wondered: I meant that right clicking on a disabled back or forward button should bring up the context menu that says "Customize Toolbar...", just like clicking on any other button in the toolbar, not the back/forward history menu, which should still only be accessible when the button is active.
Summary: Menu doesn't appear when right clicking on disabled forward or back → Context menu doesn't appear when right clicking on disabled forward or back
Confirmed. We have customize in the context menus of other disabled buttons (like stop) but not back and forward.
After discussion with the Module Owner and peers it has been decided that we're not going to change the behavior of context clicks on the navigation buttons. The thinking is that having context clicks on disabled buttons which are different than on enabled buttons would be odd and better to not have any menu at all than to have a different one. Thanks for testing Phoenix and reporting bugs.
oops, forgot to actually resolve it.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
I'm not reopening this because I don't want to be too much of a pain. I just feel that I could have made a better job explaining my point. Here goes one more time. My reasoning is that when a button is disabled, it doesn't actually exist but it's "just another part of the toolbar". So it wouldn't actually be another menu for the disabled button, but the context menu of the toolbar, at least from a user's point of view.
point noted. I'll bring it up in the next design discussion. If the module owner's position changes we'll reopen this bug or file a new one and cc: you. Thanks for the followup and thanks for testing phoenix and reporting bugs.
Status: RESOLVED → VERIFIED
I kind of agree. 98% of the time forward is disabled, and it's the biggest "open" spot on the toolbar to click to try and customize. Maybe I just keep clicking it because so many other toolbar areas you can't use to customize yet (menu bar, bookmarks toolbar, tab bar...), and I removed the stop button. But I see both sides of the argument, and once the bug for menu/bm toolbar is fixed, this will be less of an issue.
Taking QA Contact
QA Contact: asa → bugzilla
*** Bug 216726 has been marked as a duplicate of this bug. ***
*** Bug 336243 has been marked as a duplicate of this bug. ***
QA Contact: bugzilla → toolbars
You need to log in before you can comment on or make changes to this bug.