[RESOLVED] Homebanking

[Virgos]

Hi,
I am experiencing a weird problem with my home-banking and NoScript. I have already read the FAQ (question 3.3, the answer to which is "Those services use JavaScript intensively also in subframes and dialogs which not necessarily have the same URL as the login page. Easiest (even if not safest) thing you can do to fix your problem is right-clicking on the page, opening the NoScript menu and Allowing the base domain (i.e. hotmail.com or google.com) rather than the full URL").
The thing is: I am not able to use my home-banking (Banco do Brasil: http://www.bb.com.br) even if I allow javascript globally. I am able to see the virtual keyboard (for entering my password), I am able to enter my password. But after that, Firefox freezes, the CPU use of my computer climbs to 100%, the cooler (ventilator) starts and doesn't stop till I "kill" Firefox.
The only way of accessing my home-banking is by deactivating NoScript and restarting Firefox every time I have to use the bank services.
I have always thought that the option "Allow javascript globally" was the same as not having NoScript installed (or running). As I see now, there is a difference.
It is very annoying having to deactivate NoScript (through the "Tools" Menu) and restart Firefox every time I have to use my home-banking (and activate it and restarting again after using it).
Does someone have an idea of what to do to solve this problem? (unfortunately, the problem occurs only after entering the password, so only those with a bank account may see it).
Thank you in advance for any help.
Virgos
PS. when NoScript is deactivated, I see a "Java Icon" while the virtual keyboard is loading. When NoScript is activated (even with the option "Allow javascript globally") this "icon" doesn't show up.

[Giorgio Maone]

Sounds like a Java plugin bug.
Could you check if your JRE is the most up to date available from Sun?
Could you also check if the problem exists on a Windows box?
Thanks!

[Virgos]

Hi,
Thank you very much for your prompt answer. Things got even stranger.
Tried on Windows (same configuration: Firefox 3.0.10; Java 1.6.0-13; NoScript 1.9.2.4) and it worked fine.
Back to Linux (Ubuntu 9.04), and it worked either (although I have alread tried hundred times before, without success). Just like magic...
In any case, thank you very much for your help. Although I don't know what was the problem, it is now gone.