Closed
Bug 259567
Opened 20 years ago
Closed 14 years ago
No lock icon on secure pop up window
Categories
(SeaMonkey :: Security, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: david.balazic, Unassigned)
References
()
Details
(Keywords: qawanted)
Attachments
(1 file)
6.60 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 The online bank ( see URL ) I use has a pop up windows for selecting a date. This windows has no lock icon to show, that it is secure. ( see attached picture ) Reproducible: Always Steps to Reproduce:
Reporter | ||
Comment 1•20 years ago
|
||
Comment 2•20 years ago
|
||
We need a way to reproduce this.... (and this is in Mozilla, not Firefox, right?)
Keywords: qawanted
Comment 3•20 years ago
|
||
How about javascript:open("https://bugzilla.mozilla.org","","status=yes,height=400,width=300") the dom.disable_window_move_resize pref must have the default value of false. Confirming. Dependency isn't quite right but close enough for now. Firefox does not have the same problem since it doesn't have as much cruft in the status bar. The problem in mozilla is that the launcher icons and the progress section don't collapse and take up a minimum of 270 pixels. Then there's the online/offline icon and possibly the p3p icon (why am I getting that? I've tuned off p3p) before you get to the lock icon.
Comment 5•20 years ago
|
||
Even with the minimum width Firefox appears to show the site name and part of the lock icon in the status bar. Theoretically there could be extension-added status bar cruft that would cause the same issue in Firefox, but for now this is seamonkey-only.
Updated•20 years ago
|
Flags: blocking-aviary1.0.1?
Updated•20 years ago
|
Flags: blocking1.7.6?
Flags: blocking1.7.6-
Flags: blocking-aviary1.0.1?
Updated•20 years ago
|
Updated•16 years ago
|
Assignee: dveditz → nobody
Product: Core → SeaMonkey
Comment 6•15 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 7•14 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•