Closed
Bug 585350
Opened 15 years ago
Closed 12 years ago
Advanced Charts on Fidelity.com do not work correctly
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bmaryano, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Fidelity Investments' Advanced Charts never worked with Firefox on the Mac (MacBook Pro), neither the new version nor prior versions. The Advanced Charts also do not work correctly with Google Chrome or Apple Safari on the Mac. They do work perfectly with MS Internet Explorer on a PC or a PC within my Mac (VM Ware Fusion). Possibly a JavaScript plug-in issue?
Reproducible: Always
Steps to Reproduce:
1. Go to Fidelity.com and log on to one's account
2. Get a stock quote on a pop-up page
3. Select detailed quote at bottom of page
4. Select Snapshot for stock
5. Select Advanced Chart
6. Attempt to use the functions on this Advanced Chart page
Actual Results:
Lack of functionality. No charts appear and nothing works.
Expected Results:
Full functionality, as when using MS Internet Explorer on a PC or a PC within my Mac.
My JavaScript is up to date. Google Chrome and Apple Safari on the Mac show the charts but do not function properly. Need to have a Fidelity account to log on in order to access Advanced Charts.
Updated•14 years ago
|
Version: unspecified → 3.6 Branch
Comment 1•12 years ago
|
||
Reporter, do you still see this problem when using a current version in safe mode? http://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode
If you no longer see the problem, please set status to resolved and resolution to WORKSFORME.
If you do see the problem, please update comments on how to reproduce.
Whiteboard: [closeme 2014-02-01]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-02-01]
You need to log in
before you can comment on or make changes to this bug.
Description
•