BankofAmerica.com Unable to Edit Payees

[therube]

BankofAmerica.com, Online Bill Pay Center - Unable to Edit Payees Information

(A more general) URL: https://sitekey.bankofamerica.com/sas/signonScreen.do
Bill Pay URL: https://bills.bankofamerica.com/wps8109 ... c51e41776d ..........

JavaScript is REQUIRED for Online Bill Pay.

On the Bill Pay site, they list all your different vendors that you have set up for payments.
Normally you can click on a vendor to edit it's payee information.

Instead you get:

Code: Select all

[NoScript XSS] xss.reason.[Exception... "Component returned failure code: 0x804b001e [nsIDNSService.resolve]"  nsresult: "0x804b001e (<unknown>)"  location: "JS frame :: chrome://noscript/content/ChanUtil.js :: anonymous :: line 86"  data: no] --- undefined

NoScript 1.9.3.5, SeaMonkey 1.1.16.
Plugins looks pretty much defaulted at the moment, disabling XSS makes no difference.
Each click on a vendor generates the above error.

(No time to investigate further at the moment ...)

Lost power momentarily in a T-Storm, so logged back in ... bla bla bla ... & this time it worked, so no sense in anyone looking at this at this time. I'll see if I can duplicate at a later point though.

Ordinarily I visit BoA with JavaScript disabled. Go to Bill Pay. Once in, I enable JavaScript. Then I went to edit a payee.

Just now I went to BoA with JavaScript enabled from the get go. Will try later to see if my "normal" way of entry again results in a failure.

[GµårÐïåñ]

I have had this problem with BofA for a while now. Here is how I get it to work, although its annoying. Middle click on the item and when it opens in a new tab, it will be expanded allowing you to edit it. It tends to happen with debit items for some reason. I have talked to them about it but they seem to be clueless.

[therube]

Can't seem to duplicate my issue.

[Giorgio Maone]

There's a bug in current ABE implementation which aborts the connection early if there's a DNS error, instead of giving you the regular "Address not found" error page.
I'm fixing that, but it means that your first attempt would have failed anyway, even though with an error page.
Probably the T-Storm hit the DNS or the network before your PC.