Closed Bug 475060 Opened 15 years ago Closed 14 years ago

FF will not load the Expenses worksheet. It worked in the previous verson of FF. IE will load this.

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: sglinge, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-11-01])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

This is a Retirement Calculator tool, one of the best on the web. To use it properly, one must fill in a progression of worksheets with personal financial data. The tool fails at the Expenses Worksheet and thus will not calculate the results.

Reproducible: Always

Steps to Reproduce:
To demonstrate, fill in a few fields starting on the General Worksheet,click save, next. 
Then do same with the next sheet and so on.
You will get the error on the Expenses Workssheet (fourth one).


Expected Results:  
The Expenses Worksheet should open to allow one to place data in fields, then save it to see the Projections and Results Worksheet.
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.