Closed
Bug 612137
Opened 14 years ago
Closed 14 years ago
doubleclick on #appmenu-button doesn't terminate firefox
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 574973
People
(Reporter: fox_trnohi, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
Up to now Firefox 3.6 terminates once you doubleclick on the upper left corner.
That doesn't work anymore once you use #appmenu-button (disabling menu-bar).
As terminating a window with a doubleclick on the upper left corner is a standard behaviour for any programm I would like to suggest implementing this.
It will definitley improve usabilty for every one using this feature.
Reproducible: Always
Steps to Reproduce:
1. Disable Menu-bar
2. Doubleklick on #appmenu-button
Actual Results:
The new menu bar opens on first klick on closes on second klick
Expected Results:
Close the Firefox Window.
If its the last open Firefox Window: terminate process.
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Hi Kevin,
I read through bug 575248 - it is only concerned about what happens when double-clicking on the tabs-area.
What I am suggesting is left from the tabs area: a button that opens the Firefox menu.
I am chaning the bug back to unconfirmed. I you still thin it is a dublicate, please let me know why.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 3•14 years ago
|
||
I also feel like 575248 does not describe this problem. Could the status of this be revaluated? I see this as a major inconvenience when using firefox.
Firefox should not break platform standards.
Comment 4•14 years ago
|
||
Not sure how I got the wrong bug number. Meant to grab 574973. Sorry but this won't be happening. See bug 574973 comment 19 for details.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•