Closed Bug 164542 Opened 22 years ago Closed 22 years ago

URL bar unresponsive when new browser window created while Mail/News is minimized

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 82534

People

(Reporter: ellis, Assigned: samir_bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530

The URL bar is unresponsive in a particular situation when Mozilla is started
"again" (i.e. clicking Mozilla icon in Start Menu while it's already running).  

If a browser window is already open and you start Mozilla again (from the Start
Menu), a new browser window will be created and everything is fine.  This bug
only happens when Mail/News is all that is open and it is minimized.  If you
restore the Mail/News window and switch back to browser window, the URL bar will
resume functionality.

Reproducible: Always

Steps to Reproduce:
1.  Start Mozilla.
2.  Open Mail/News
3.  Close any and all open browser windows.
4.  Minimize Mail/News.
5.  Start Mozilla again (from the Start Menu or other desktop icon).


Actual Results:  
URL bar will not allow typing or deletion of current text (start page URL).

Expected Results:  
URL bar should work!

Using Modern theme
I just tried this with build 2002082304-TRUNK on Win98SE, and I don't see any
problem. Try upgrading your version of Mozilla and see if that fixes your problem.

*** This bug has been marked as a duplicate of 82534 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
thanks for the great bug report Rich!

the fix was checked into mozilla on 2002/06/19.
and it looks like you're using the 1.0.

try 1.1, it's far more stable, and should (almost completely) resolve this bug.

file another, if you find it using the latest builds.

Thanks.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.