User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:126.96.36.199) Gecko/2008120122 Firefox/3.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:188.8.131.52) Gecko/2008120122 Firefox/3.0.5 Action: internet banking After completing the transfer form, the button "verzenden" (sending) was clicked on, but nothing happened. Using another browser, same action worked well. Had the same problem yesterday to send a filled-in form to another bank. Reproducible: Always Steps to Reproduce: 1.Start browser 2.Select Bank from 'Bladwijzers'and log in 3.select 'overschrijven' 4.Fill in the form 5.select button: 'Opslaan,naar verzendlijst' 6. fill in the TAN code. 7. click button 'verzenden'. Actual Results: nothing happened Expected Results: transfer accepted by message from the bank 'uw opdracht is verwerkt'. send my transfer order.
Difficult to test because you need Username/password/TAN. Nothing we could do without a testcase
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090115 Minefield/3.2a1pre Yeah, I've seen this too, but like matti says, it is not something that can be tested and fixed without a testcase. Would cost me a lot of money to find a regression range (if it is a regression). And I'm even not sure that it isn't caused by an extension.. I think this should be corrected by the bank, should be easy to do.
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.