Closed
Bug 287545
Opened 20 years ago
Closed 20 years ago
I downloaded 1.0.2 this morning, no longer displays webmail logon page
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: richard.a.frear, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Previously, using build 1.01, I was able to logon to may cable ISP web mail page. This morning I installed build 1.02. I was hoping you fixed the quality feedback agent wanting to report user initiated exiting of Firefox as a crash. You didn't, but this bug report is not about that. To test your build, I went to my cable ISP webpage to see if I could log onto the webmail function. I could not. When I click on the webmail icon, a firefox browser instance is started that opens the same page. I am not presented with the weblogin page. BTW, I had logged in using build 1.01 this morning, logged out, then installed build 1.02. The first time I logged into the webmail, Firefox used my previous cached login credentials and brought up the webmail page. Which I thought was odd. I rebooted the computer, which cleared the cache, and I have the problem reported above. Additionally, while writing this, I took the time to login to the webmail page using IE. It works fine. Reproducible: Always Steps to Reproduce: 1. go to www.optonline.net 2. Select "webmail" icon 3. Actual Results: loads home page again in a different firefox browser instance. Expected Results: loads webmail login page in a different firefox browser instance.
Do you have any extensions or themes installed? what happenes when you try with a new profile (run firefox.exe -p to create a blank test profile.) wfm, i get send to https://webmail.optonline.net/
Summary: I downloaded 1.02 this morning, no longer displays webmail logon page → I downloaded 1.0.2 this morning, no longer displays webmail logon page
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050323 Firefox/1.0+ WFM on latest Trunk. Reporter: Try to reproduce using a clean profile. Changing severity to Normal. Changing version to 1.0 Branch. CCing myself
Severity: critical → normal
Version: unspecified → 1.0 Branch
| Reporter | ||
Comment 3•20 years ago
|
||
I tried reproducing as suggested below, using <firefox.exe -p>, using a "clean" profile. The webmail login page was displayed, after first warning me that I was about to display an encrypted page. Extensions: Autoform 0.5.8 Themes: Firefox(default) 2.0 I uninstalled the Autoform, still have problem. BTW, someone downgraded this problem to "normal". I am not part of the design team. But if a product I was working on had a problem that caused a user to use a competitors product, no way would it be a "normal" problem. You all should change your mode of operation, you are supporting a product in "production" now. Regards, Richard Frear
(In reply to comment #3) > I tried reproducing as suggested below, using <firefox.exe -p>, using > a "clean" profile. The webmail login page was displayed, after first warning > me that I was about to display an encrypted page. Looks like the problem resides in your normal profile then, as it works with the clean profile and with my profile. POSSIBLY, but not definitely, caused by the extension. > BTW, someone downgraded this problem to "normal". in bugzilla terminology we use certain definitions for severity and "criticial" describes: "crashes, loss of data, severe memory leak" which does not describe your bug. MAJOR "major loss of function" would be more appropriate -> bumping to major. Can you provide reproducible steps that cause the profile corruption? Maybe you've blocked certain relevant cookies?
Severity: normal → major
| Reporter | ||
Comment 5•20 years ago
|
||
After uninstalling the Autoform and re-booting my Windows XP Pro computer, I no longer have the problem. Something in Autoform 0.5.8 was causing a problem I identified. Regards, Richard Frear
problem caused by extension -> not something we can fix in the firefox code. -> invalid "The problem described is not a Firefox bug."
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•