Closed Bug 47620 Opened 24 years ago Closed 24 years ago

Security padlock doesn't change until secure page loading completes

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: adamlock, Assigned: ddrinan0264)

References

()

Details

(Whiteboard: [branch accept][rtm-])

When I load the above URL, the status padlock doesn't change to "Signed by Verisign Trust Network" until the entire page (including graphics) has loaded. This can take 20 seconds or so on a dialup link. In 4.x, the security padlock turns yellow immediately after downloading begins.
Summary: Security padlock doesn't until secure page loading completes → Security padlock doesn't change until secure page loading completes
->Crypto for PSM UI issues.
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: czhang → junruh
Keywords: nsbeta3
Blocks: 48444
Setting target milestone to future.
Target Milestone: --- → Future
Until the entire page has loaded, the user is not necessarily seeing what the site intended. This could be considered INVALID.
I agree with jgmyers. Invalid.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Verified invalid.
Status: RESOLVED → VERIFIED
4.x sets the lock icon immediately -- are you saying 4.x is broken? This is _very_ disconcerting to users since they very easily think (as I did) that the document was not secure and get very very scared.
Severity: normal → major
Status: VERIFIED → REOPENED
Keywords: rtm
OS: Windows NT → All
Hardware: PC → All
Resolution: INVALID → ---
ccing people, and opening for discussion.
It looks like the icon switches instantly to "unlocked" as you begin *any* transition (even SSL to SSL site), and only switches back to "locked" when it is sure the page has no mixed content (combo of httpS with http). From a security perspective, we're erring on the side of avoiding false claims of security. I think that the fact that N6 does incremental layout, starting asap, makes this "feature" very visible (as compared with 4.x). I think that 4.x displayed an open lock when mixed content is displayed, but 4.x didn't display much until it had the entire page. I think that if it appears that 4.x switches "instantly" to a locked icon it is because it waited to display anything until it had pretty much the entire page. I'm open to being corrected... but I suspect this plays into making this "feature" more visible in N6. There has also been a lot of discussion about mixed content in N6. Perhaps, if we settle on not complaining about mixed content, we could show the locked icon sooner... but until this is much more settled, I think showing an unlocked icon until we are "sure," is probably the most reasonable activity.
jar, that might be reasonable to you, as someone very knowledgeable about the details of security. 99% of our users are not. All they see is their personal data on the screen with no hint of security (users don't know what https means, and they certainly don't know what mixed content is).
rtm-, the behavior is correct if not elegant.
Whiteboard: [rtm-]
After the fix to bug 31982, the lock icon shows locked immediately after downloading begins, but will not have the "Signed by" popup until the entire page is loaded.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
junruh - pls state which trunk build you verified on. Thanks.
Verified on 12/21 Mac, Win and Linux trunk builds.
Added branch accept to status whiteboard
Whiteboard: [rtm-] → [build-accept][rtm-]
Whiteboard: [build-accept][rtm-] → [branch accept][rtm-]
David, please check in on the branch ASAP.
ddrinan is on sabatical. jgmyers: can you check this in since you know something about this bug?
This bug is fixed by the patches attached to bugs 31982 and 59827. No additional changes needed.
Verified on the latest MTEST builds on Win, Mac and Linux.
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: Future → ---
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.