Closed
Bug 351636
Opened 19 years ago
Closed 17 years ago
empty sidebar when proxy requests password
Categories
(SeaMonkey :: Sidebar, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: hwachter, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060729 SeaMonkey/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060729 SeaMonkey/1.0.4
When starting the browser behind a firewall requesting for a password, sometimes the sidebar is empty. Restarting only the browser window doesn't help. I have to close all mozilla windows, restart the browser and hope the best! Sometimes the sidebar is empty during password request and appears after typing the password, but often (50%) not. This behaviuor is an very old one. I hoped that it would be solved in each new version.
Reproducible: Sometimes
Steps to Reproduce:
1. start seamonkey behind a proxy requesting for a password
2. type in seamonkeys masterpassword
3. klick ok for the offered proxy account and password
Actual Results:
Browser shows the starting page, but sidebar is empty and filld with an explanation how to create sidebars
Expected Results:
show my original sidebar
First time I fear that my sidebar may have disapeared, but the bookmarks.html was still present and will come back if the start is more successful
Summary: emty sidebar when proxy requests password → empty sidebar when proxy requests password
Comment 1•17 years ago
|
||
Could you verify whether you experience this issue in a recent release of SeaMonkey? Please also consider resolving this if all is well. Thanks.
http://www.seamonkey-project.org/releases/
Updated•17 years ago
|
Version: unspecified → SeaMonkey 1.0 Branch
Comment 2•17 years ago
|
||
(1,5 months later)
No reply from reporter.
SeaMonkey v1.0.x is not supported anymore.
(Would have been "Incomplete", now is) R.Invalid
Reopen if you can reproduce with SeaMonkey v1.1.9.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•