Closed Bug 310690 Opened 20 years ago Closed 17 years ago

window and status bar won't stop flashing after displaying a notification dialog

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: aditsu, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051001 SeaMonkey/1.1a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051001 SeaMonkey/1.1a When I get a notification from the browser (such as: "Security Warning, You are about to leave an encrypted page ..."), the window title and status bar start flashing. That's ok, except that in this build they won't stop, but just keep flashing forever. Very annoying. Reproducible: Always Steps to Reproduce: 1. I first experienced this when logging on to yahoo mail, but it can probably be reproduced in different ways. So, first I went to https://login.yahoo.com/config/login?.src=ym for secure login 2. I entered my user name and password 3. After the login, the website redirected me to the (non-ssl) inbox. That's when the browser warned me (as expected) that I was going to a non-encrypted page. Actual Results: The window and status bar kept flashing. They're still flashing right now as I am typing. Expected Results: Flash maybe 3 times then stop.
Hm, it doesn't seem to be always reproducible. I'm investigating it more.
Hm, I can't reproduce it now. But it actually happened. I guess you can close it, unless you have another suggestion.
I saw this too with SeaMonkey 1.0a but also didn't find a way to reproduce it. The only way to work around that was to quit SeaMonkey and open it again.
Resolving worksforme - Yahoo mail certainly works on 1.1.9, and can't replicate this elsewhere. Please see if you experience this issue with a newer release. Thanks. http://www.seamonkey-project.org/releases/
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.