Closed
Bug 243076
Opened 21 years ago
Closed 15 years ago
Can not minimize running Mozilla windows by clicking on taskbar button if Explorer.exe is restarted.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: alexeyc2003, Unassigned)
Details
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8a) Gecko/20040423
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8a) Gecko/20040424
Firefox/0.8.0+
Thunderbird version 0.6 (20040502)
In Windows starting with version 2000 I think, not only you can restore/focus a
window by clicking on its taskbar button, but you can also minimize focused
windows by clicking on their taskbar buttons. Sometimes Windows shell process
Explorer.EXE might freeze and needs restarting. So you usually kill the process
and restart it again, and everything (or almost everything) goes back to normal.
However Seamonkey, Firefox and Thunderbird windows stop responding to minimize
clicks on taskbar buttons.
Steps to reproduce:
1. Run Mozilla.
2. Kill Explorer.EXE process in task manager.
3. Restart it Explorer.
4. Set focus to a Mozilla window.
5. Click on taskbar button of that window.
Actual results:
The window loses focus and its taskbar button gets de-pressed.
Expected results:
The window should also get minimized.
Not all running Windows applications are able to handle this scenario. Some
behave the same way Mozilla does, but some recover gracefully and don't lose
functionality. For example IE windows do not recover the functionality, but mIRC
window does.
Also this affects only existing windows. Any new windows that you open after
Explorers restart will behave normally.
Workaround:
Restart Mozilla, or create a new Mozilla window to work in.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 1•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 2•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•