Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
Don't be sloppy in your scripts

For a few weeks now, every time I try to logoff from my home banking website something bad happens. See screenshot below.(screenshot eaten by backup failure.)

  1. Firebug opens unexpectedly
  2. There's a frigging debugger; statement in the live production site
  3. The logoff process hangs until I press F8 in Firebug or the continue button
  4. All my information is still on the screen. Imagine if I had just clicked Sign Off and left my desk.

When I saw this for the first time I though: wow, some developer will be slapped for that (actually there are some developer names in the file,) but it seems that nobody else has a debugger enabled or they just hate their clients that are also web developers. The "bug" has been there for at least 2 weeks now.

Even if you don't care for customers that happen to have a debugger like myself, leaving that kind of thing in your production environment immediately projects an image of sloppiness that is the last thing I want to have with my home banking.

Update 11/24/2008: That script was fixed sometime over this past weekend.

Posted 11-14-2008 12:05 PM by sergiopereira

[Advertisement]

Comments

Jeff W wrote re: Don't be sloppy in your scripts
on 11-14-2008 4:17 PM

This doesn't shock me at all.  There is so much bad or sloppy scripting out there it is crazy.  I'm constantly getting debug error to the point where I often turn the option of when I'm just browsing and not coding.

sergiopereira wrote re: Don't be sloppy in your scripts
on 11-14-2008 4:25 PM

@Jeff

I don't get these type of errors often but I can certainly believe there are many things like that out there - probably much worse things.

What surprises me is that in this case we are not talking about some random startup or personal site. Maybe I'm just giving too much credit to my bank (was that a pun?).

Dew Drop - Weekend Edition - November 15-16, 2008 | Alvin Ashcraft's Morning Dew wrote Dew Drop - Weekend Edition - November 15-16, 2008 | Alvin Ashcraft's Morning Dew
on 11-15-2008 9:38 PM

Pingback from  Dew Drop - Weekend Edition - November 15-16, 2008 | Alvin Ashcraft's Morning Dew

Daniel wrote re: Don't be sloppy in your scripts
on 11-17-2008 9:31 AM

I just tried the same thing, worked fine for me.  Firebug is defniitly set to debug scripts, too.

sergiopereira wrote re: Don't be sloppy in your scripts
on 11-17-2008 9:45 AM

@Daniel. Funny, I've tried it earlier today and still got that problem. My account became BofA when they acquired my previous bank. Maybe they still have some logic there to support these different types of accounts, who knows... Check if you have that debugger; line in the file cmdatatagutils.js as shown in the image.

norm wrote re: Don't be sloppy in your scripts
on 11-17-2008 5:52 PM

i don't know if this will make a difference, but they have some steps you are supposed to follow to set up Firefox to use the online banking system...

Firefox

1. Clear your cache

Go to Tools in the browser’s menu

Select Options and then Advanced

From the Network tab, under “Cache”, click Clear Now

2.  a. Delete Bank of America cookies

Go to the main Start button in the Windows menu

Select Search and then For Files or Folders…

Enter bankofamerica.com in the “Search for files or folders named” box

Select Local Hard Drives (C:) for the “Look in” box and click Search Now

Once all Bank of America cookies have displayed, select Edit from the Search Results window menu and then Select All

All cookies will be highlighted. Click the Delete button on your keyboard to delete all the cookies.

 b. Delete cookies

Go to Tools in the browser's menu

Select Options and then Privacy

Click Show Cookies...

Select a particular site from the list and click Remove Cookies to delete cookies from that site, or click Remove All Cookies to delete cookies from all the sites in the list

3. Check your popup blocker

Go to Tools in the browser's menu

Select Options and then Content

Make sure “Block pop-up windows” is selected and then click Exceptions

Add www.bankofamerica.com to “Address of web site” area and click Allow

4. Clear private data

Go to Tools in the browser's menu

Select Options and then Privacy

Select “Ask me before clearing private data” and click Clear Now...

In the Clear Private Data popup window, select the following: Browsing History; Download History; Saved Form and Search History; Cache; Cookies; Saved Passwords; and Authenticated Sessions

Click Clear Private Data Now

5. Allow add-ons

Go to Tools in the browser's menu

Select Options and then Security

Select “Warn me when sites try to install add-ons” and click Exceptions

Enter www.bankofamerica.com in the “Address of web site” box and click Allow and then Close

6. Clear passwords

Go to Tools in the browser's menu

Select Options and then Security

Click Show Passwords..., then click Remove All, then click Close

7. Check your protocols

Go to Tools in the browser's menu

Select Options and then Advanced

From the Encryption tab, under “Protocols”, select both Use SSL 3.0 and Use TLS 1.0 and then click OK

8. Turn off Auto-Detect

Go to View in the browser's menu

Select Character Encoding

Make sure Auto-Detect is off

9. Check languages

Go to Tools in the browser's menu

Select Options and then Advanced

From the General tab, under “Languages”, click the Choose... button

Select English and click OK

sergiopereira wrote re: Don't be sloppy in your scripts
on 11-17-2008 7:06 PM

@Norm. Wow, those are very thorough instructions, thanks. Unfortunately none of them deal with the debugging support in the browser.

I just tried on Firefox on a Mac and the same thing happens. That darn "debugger;" statement is there, stops everything and Firebug opens.

GR Brot wrote re: Don't be sloppy in your scripts
on 11-19-2008 4:22 PM

Perhaps the latest versions of Firebug have a failsafe as I only get the debugger on local files.  As soon as I publish them to the web and access them with http://... then the debugger no longer kicks in.

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Subscribe
Google Reader or Homepage

del.icio.us CodeBetter.com Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl CodeBetter.com Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of Devlicio.us
Red-Gate Tools For SQL and .NET

NDepend

SlickEdit
 
SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
LiteAccounting.Com
DevExpress
Fixx
NHibernate Profiler
Unfuddle
Balsamiq Mockups
Scrumy
JetBrains - ReSharper
Umbraco
NServiceBus
RavenDb
Web Sequence Diagrams
Ducksboard<-- NEW Friend!

 



Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers

 

Community Server (Commercial Edition)