Closed
Bug 775473
Opened 12 years ago
Closed 8 years ago
Command-W Should only close current Tab; closes entire viewer window
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: 99e86ee5, Unassigned)
Details
User Agent: Mozilla/5.0 (masking-agent; rv:14.0) Gecko/20100101 Firefox/14.0.1 Build ID: 20120713134347 Steps to reproduce: Close a singular tab using the Command+W shortcut on MAC OS X 10.7.4 using the new 14.0.1 firefox. Actual results: Upon pressing command+w, the whole window closes. Whats more irritating, upon reopening a firefox window, I cannot restore session. Presumably because I never physically closed firefox and only closed the window. However upon reopening and testing the command+w, it seems to work for a short period of time, closing singular tabs. Tabs/hours later, habit of me presses command+w to close the tab and find my frustrating go through the roof due to the me losing all my tabs. This has only started happening since the 14 branch update. Expected results: Upon pressing command+W, the current; target singular tab should have closed, leaving me with all the other opened tabs I had.
Comment 1•12 years ago
|
||
Does this also happen when Firefox is in safe-mode? To do this: Open Terminal and type in /Applications/Firefox.app/Contents/MacOS/firefox -safe-mode
Comment 2•11 years ago
|
||
This happens to me on multiple MACs. It has gotten way worse under 23.0.1.
Comment 3•10 years ago
|
||
(In reply to Jonah Ho (FireChemist) from comment #1) > Does this also happen when Firefox is in safe-mode? > > To do this: > Open Terminal and type in /Applications/Firefox.app/Contents/MacOS/firefox > -safe-mode it happens in safe mode?
Flags: needinfo?(99e86ee5)
Hi, Marking this as Resolved: Incomplete due to the lack of response from the reporter. Reporter, please feel free to reopen it if you are still having this issue. Thank you for your time.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(99e86ee5)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•