Closed
Bug 100787
Opened 23 years ago
Closed 22 years ago
Pressing ESC while moving between HTTPS pages causes spurious warning
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 140836
Future
People
(Reporter: greenrd, Assigned: KaiE)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4+) Gecko/20010919 BuildID: 2001091908 If you go to a https: site and click on a https: link, but press ESC immediately, you get a spurious Security Warning dialog saying that you are leaving encrypted mode (as long as you haven't disabled that warning). Reproducible: Always Steps to Reproduce: 1. If necessary, create a new profile to ensure that this warning dialog will appear 2. Go to https://sourceforge.net/ 3. Click on login via SSL on left hand side 4. Very quickly press the ESC key Actual Results: The standard Security Warning dialog appears that tells you you are leaving encrypted mode - but you aren't! Sometimes the page continues to load in the background. Expected Results: Not display the dialog.
Comment 1•23 years ago
|
||
over to PSM
Assignee: asa → ssaux
Component: Browser-General → Client Library
Product: Browser → PSM
QA Contact: doronr → junruh
Version: other → 2.1
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Future
Comment 3•23 years ago
|
||
I cannot reproduce this. Reporter, can you try a later build?
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•23 years ago
|
||
Bug still here in build 2001102806. You have to be quite quick. If necessary slow down mozilla. Also, the security icon now displays as insecure for the loaded page - but the URL bar displays the https: URL. Upgrading from trivial to minor.
Severity: trivial → minor
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 5•22 years ago
|
||
I can reproduce this bug. Pressing ESC did not cause the problem, but clicking the stop button did it. This bug is due to the current implementation approach of the security state tracking. This will behave correctly, after bug 62178 has been fixed.
Assignee | ||
Comment 6•22 years ago
|
||
This should now be fixed. *** This bug has been marked as a duplicate of 140836 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•