Closed
Bug 270716
Opened 20 years ago
Closed 19 years ago
Alerts when I tried to close a popup that is in the process of trying to establish a secure connection.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: mmarcus, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 This is a wierd, mainly cosmetic bug actually. I was researching a domain name registration at: http://www.networksolutions.com/en_US/whois/index.jhtml After entering the domain name and viewing the record for it, I closed the tab I had opened for networksolutions. Upon closing the tab and leaving the networksolutions web site, networksolutions automatically sends a large popup, then a small popup with a secure connection. The problem is that I right-clicked the small popup window on the task bar and selected "Close" before the popup had fully loaded. This caused Firefox to generate an alert saying something about https protocol not supported. I kept clicking OK on the alerts which recurred repeatedly while I also tried to close the popup window, each time adding https to the description of the offending protocol as in: https httpshttps httpshttpshttps, etc. This has got to be a timing bug that then caused an endless loop in the close window/security connection threads related to the popup window. Fix would be to kill the popup's thread which is trying to establish a secure connection upon the user opting to close the popup window. This is a minor bug as I tend to be really quick on the keyboard/mouse when browsing the internet. Most users will not likely encounter it. Reproducible: Sometimes Steps to Reproduce: 1. Any site which throws (generates) popup windows upon leaving their site. 2. User right-clicks the popup window's button on the task bar before the popup's secure connection has been fully established. Probably only occurs when interrupting the establishment of a secure https protocol for the popup, since that's two way activity. 3. Actual Results: Endless loop of clicking OK on the alert messages and trying to close the popup window. Expected Results: Fix would be to kill the popup's thread which is trying to establish a secure connection upon the user opting to close the popup window. In other words, if the user selects to close the popup window (or tab or new window for that matter), then all connection protocols for the window to be closed should be terminated immediately without throwing any errors.
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•