Closed Bug 249975 Opened 22 years ago Closed 22 years ago

I fill the search form and press "Search" button. Security warning window does not close after pressing OK button

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: maximus-2000, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 I have a SMP machine with Windows 2000 SP4. When I see such windows as security warning ( "The information you have entered..." ), alert, they don't close after pressing OK or Cancel button. In order to get it closed, I should move this window from the center of screen to the border. Reproducible: Always Steps to Reproduce: 1. Go to url http://bugzilla.mozilla.org/query.cgi 2. Fill the form 3. Press "Search" button 4. Press "Ok" in security warning window Actual Results: Security warning window is not closed Expected Results: Security warning window is closed Windows 2000 Professional, SP4, two Pentium III - 500 Mhz processors on ASUS mainboard. Matrox G400 drivers version 5.92.006
maximus-2000@mail.ru - 20031007 is too old a build to report bugs against now. The problem you are reporting may well have been fixed already. Could you please download a recent nightly build from ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/, and then report back on the status of this problem? Thanks
(In reply to comment #1) > Could you please download a recent nightly build from > ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/, and then report back on > the status of this problem? Well, this build works fine. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040706
Since the reporter no longer sees this bug in recent builds, marking as WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.