Right-clicking on bottom half of tab bar does not produce a context menu when the menu bar is toggled to show via the ALT key

NEW
Unassigned

Status

()

Firefox
Toolbars and Customization
9 years ago
9 years ago

People

(Reporter: u88484, Unassigned)

Tracking

({regression})

Trunk
x86
Windows Vista
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: wontfix?)

(Reporter)

Description

9 years ago
Right-clicking on bottom half of tab bar does not produce a context menu when the menu bar is toggled via the ALT key.

STR:
1) View->Toolbars, uncheck the 'Menu Bar' entry
2) Toggle the menu bar via the alt key
3) Right-click on the lower half of the tab bar

No tab bar right-click context menu

4) Toggle the menu bar via the alt key
5) Right-click near the above the top half of the tab bar

The tab bar right-click context menu shows.

To reproduce to get the context menu, you actually half to right-click a few pixels above the middle section of the tab bar, not just above the center.
(Reporter)

Updated

9 years ago
Blocks: 456535
No longer depends on: 456535
(Reporter)

Updated

9 years ago
Summary: Right-clicking on bottom half of tab bar does not produce a context menu when the menu bar is toggled via the ALT key → Right-clicking on bottom half of tab bar does not produce a context menu when the menu bar is toggled to show via the ALT key
This might be suboptimal, but it's pretty much expected. The menu bar hides on mouse-down (which will shift the tab bar up), the context menu opens on mouse-up (unless the tab bar isn't there anymore). IE behaves the same way, fwiw.
Whiteboard: wontfix?
(Reporter)

Comment 2

9 years ago
I understand and see the logic behind it but use the same STR but right-click on the menu bar instead and you get that right-click context menu no matter where you right-click, even though if the mouse-up event is over the tab bar.
Yep, mouse-down on the menu bar is special cased, so that you can access the menu bar's context menu even with auto-hiding enabled.
You need to log in before you can comment on or make changes to this bug.