Closed
Bug 309266
Opened 19 years ago
Closed 18 years ago
Login Problem from default Profile , but when used diffrent profile no problem.
Categories
(SeaMonkey :: Passwords & Permissions, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: sahir14, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 I am using PHP5 and Apache2.0 on suse9.1 machine for developing login web application. With use of Mozilla 1.7.5 browser with default profile manager, after giving login info, page dosen't go to next page showing the same login page. But when i tried the same from diffrent profile in same Mozilla , it worked fine. Reproducible: Always Steps to Reproduce: 1.using my local url for testing 2.giving login info 3.click 'Enter' or click submit button Actual Results: Same login page displayed Expected Results: It should go to another page I am using 'Modern' Theme. I have tested on Netscape IE and on same mozilla browser with diffrent profile , its working fine, but not with default profile
Comment 1•19 years ago
|
||
Do you have any extensions installed in your profile? How does your webapp work, does it use cookies? You know, testing this without a testcase or a URL is somewhat difficult ;-)
Comment 3•19 years ago
|
||
You'll need to either determine what part of your profile is important (migrate your default profile to a clean one a bit at a time until the clean one is broken) or determine specifically why the web app delivers the wrong page (since you have access to the server). Also, please try a more recent build (SeaMonkey 1.0a).
Assignee: nobody → form-submission
Component: Profile: Manager → HTML: Form Submission
Product: Mozilla Application Suite → Core
QA Contact: profile-manager → ian
Version: unspecified → 1.7 Branch
Comment 4•19 years ago
|
||
Doesn't sound like a form submission issue.
Assignee: form-submission → dveditz
Component: HTML: Form Submission → Password Manager
Product: Core → Mozilla Application Suite
QA Contact: ian
Updated•19 years ago
|
Assignee: dveditz → nobody
This is resolved by using fresh installation of Mozilla.
Previous comment says it was resolved by reinstalling Mozilla a year ago. IMO this bug no longer needs to remain open.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•