InformAction Forums

I have now moved from my iMacPC, back to my old Windows PC which I have been using this last two weeks while the iMac was being repaired and I have updated NoScript to the lastest 2.6.6 version. Now this PC works just fine on the Lloyds Bank Website using Firefox 20.0.1 and NoScript 2.6.6. The probl...

I think you have hit the prime source of my problem - I was using a very old version of Firefox (Version 10). The background is that I abandoned my Windows PC just over a year ago and moved to Apple iMac. Unfortunately the iMac died with a Login Board/Power Supply failure and had to go back under ex...

Current position: Friday 19 April. As a result of following support from Giorgio Maone & The Rube:Ambassador I have now discovered that if I use Versions 2.6.6/RC4 or earlier my Internet access to Bank Website AND THIS FORUM WEBSITE performs correctly. However if I use Versions 2.6.6/RC5 or late...

I have now set to 2.6.6 rc5 and taken a copy of the Lloyds error message which I will now attempt to copy to this forum page with the browser still in2.6.6/rc5 condition: XML Parsing Error: no element found Location: https://online.lloydstsb.co.uk/personal/primarylogin Line Number 1, Column 1: That ...

In answer to Giorgio Maone: When anyone wants to Log-on to the Online Lloyds Bank system you go to Web Page https://online.lloydstsb.co.uk/personal/logon/login.jsp (anybody can get this initial page, and you have to enter the usual User ID and password and hit return. The bank system then checks the...

I have done as you asked and I found that Version 2.6.6 works for rc1, rc2, rc3 and rc4 but fails on rc5. Using ctrl,shift,J gave an error message on rc5 stating Error: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628. Source File: chrome://brows...

I am just a non-tecki user of NoScript on Firefox for last few years and have always used the NoScript Add-0n for my own protection. However today I had one of the routine updates to NoScript which I automatically "allowed". However this latest version 2.6.6 immediately blocked access to m...