Closed
Bug 159604
Opened 22 years ago
Closed 22 years ago
Compound addresses do not work
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 159589
People
(Reporter: vfjlev, Assigned: Matti)
References
()
Details
ALL compond addresses, e.g which contain / will stop working, returning error : "URL missing". It started in Netscape 7.0 and Mozilla 1 after both worked OK for weeks, and also recently in Mozilla 2002072203, it seems that going to Netscape 4.79 somemtimes cures the problem for some time. Will appreciate suggetion to trash prefs etc.
Reporter: could you please read the Bug Writing Guidelines at http://www.mozilla.org/quality/bug-writing-guidelines.html to see the kinds of information we need in a bug report. Please report back with more information (like BuildID and steps to reproduce) after reading those guidelines and consider using the Bugzilla Helper to report future bugs. The Helper can be found at http://www.mozilla.org/quality/help/bug-form.html Thanks for your help in testing Mozilla. P.S. Please note that tester pre-screening the bugs have the authority to dismiss poorly described bugs we cannot get enough usable information from. In your case, we lack the step-by-step instructions on reproducing the bug.
Comment 2•22 years ago
|
||
Reporter: do you have Mozilla and Nestcape 6/7 installed on the same computer ? You must /not/ share profiles between them.
Assignee | ||
Comment 3•22 years ago
|
||
Reporter: Have you installed Mozilla over an older build ? If yes do this : uninstall mozilla, delete all files in c:\programs\Mozilla.org\Mozilla\ (but save your plugins) and reinstall mozilla. If you still see the problem try "mozilla -profilemanager" and create an additional test profile.
Assignee | ||
Updated•22 years ago
|
Severity: blocker → major
Comment 4•22 years ago
|
||
*** This bug has been marked as a duplicate of 159589 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•