Sorry, it's about:config (with a colon). However, I can't think of any reason that Chase you have to go into that preferences editor. Are you sure this advice is legitimate and not an impersonator??

If you describe the problem you're having with the site and what preference Chase thinks you should change, we can advise on whether it sounds like a good idea.

---

Do you use the NoScript extension by any chance?

Here's a screen shot (without pictures) of the Chase instructions (which I see I mis-read!! time for reading glasses):

Close Window Close Window Thursday, June 9, 2011 Making Chase.com a Trusted Site PrintPrint

Note: If you use Internet Explorer 6.0 + or Mozilla Firefox and do not make Chase.com a trusted site, page information may not display or may not display properly. Instructions for Mozilla Firefox users Instructions for Internet Explorer 6.0+ users

   Step 1: Type “about:config” in your browser’s URL field.

   Step 2: If a warning message appears, click “I’ll be careful, I promise!”

   Step 3: Scroll down to “signed.applets.codebase_principal_support.”

   Step 4: Double-click on “signed.applets.codebase_principal_support” and “Value” will change to “true.”

   Step 5: Log on to Chase Online.
   Step 6: Click “Payments & Transfers tab.”
   Step 7: Click “Fraud Protection Services” subtab.
   Step 8: When presented with the Internet Security message, check “Remember this decision” and then click “Allow.”

   Step 9: Repeat step 8.
   Step 10: Close the Firefox browser application.
   Step 11: Restart the Firefox browser and return to Chase Online.

See also:

• http://www.mozilla.org/projects/security/components/signed-scripts.html

I wonder why they need elevated privileges?? Well, be cautious about giving them to any other sites after you enable codebase principals.