Slashdot Mirror
Online Banking And Browser Support
robbo writes "Earlier this week, The Register ran a piece on major UK banks and E-commerce sites' refusal to support alternative browsers for online banking, and they followed up with a list of saints and sinners. The reasons vary from requiring support for proprietary technology to security. My own bank only recently started supporting Netscape 6 (but they still don't support Mozilla). Clearly, support for Mozilla, Konqueror, or Galeon are absolutely necessary if projects like GNUCash can successfully integrate online banking. How does the Slashdot crowd find their banking support? Is your bank a sinner or a saint?"
2 years ago Wells Fargo had an issue with the latest Netscape, but aside from that they've supported every Mozilla I've ever used.
Sig!
Kudos to Nationwide (UK Building Society), whose online banking site I've successfully used with Mozilla and Konqueror (3.0) as well as IE. Everything seems to work as it should.
To be fair, it's probably not the Banks etc that set the terms to limit the browsers that access their sites. It's lazy developers, which are almost certainly web-dev companies trying to complete a project that they've managed to land by bidding low.
;-)
I've been guilty of it in the past - having to rush out a project, and not taking the time to test on every browser across every platform. The "IE only" disclaimer is an excuse for the most part.
It's worth complaining to the company though, especially if you mention they're being ridiculed on a number of extremely popular tech news sites
Code, Hardware, stuff like that.
Wamu is great as far as cross-browser support. I only have two complaints:
1) They block ICMP requests. Before I fixed my firewall (forcing the MTU), I couldn't get to the site.
2) Javascript that sets focus to the Username field *after* the page finishes loading (onLoad()). If you're already typing the password at this point, you look up, and just typed it (viewable) in the Username box.
Oh, make that 3 complaints:
3) It's far from realtime...
Other than these minor issues, I have never had a problem with any SSL-capable browser on any platform (even the HTML/CSS/tables all line up correctly).
---
I cancelled my Capital One card over their refusal to allow Mozilla. Spoofing the UA header doesn't work, as they obtain this via Javascript (which must be enabled). Moz doesn't (yet?) let you override the UA that javascript returns...
I've emailed Cap One many times, and even tried to explain to the Phone Monkey when I cancelled the card why I was cancelling. Unfortunately, this person understood none of what I was saying...
Of course I've also emailed Flipdog.com, VistaPrint.com, and other sites over issues like this. Pisses me off, and I do hope AOL one day ships a Gecko/Mozilla-based browser for this reason...
NGWave - Fast Sound Editor for Windows
Things will only change if you actually do something about it. I *always* complain if I have the time, I will mail the webmaster and point out that there is an HTML standard, point them at a dodgy validation of their site via validator.w3.org, and point out that they lose money, one way or another.
So get off your ass, knock up a form letter, keep it handy, and complain!
The future is partly in your hands.
Note to ACs: I won't mod you up, even if you are being funny or insightful. So take a chance! It's not real life!
What about Opera masquerading as IE or netscape?
Capital One determines the browser using JavaScript, not the UA header. Unfortunately overriding the UA string does not override what JavaScript returns. And the site of course doesn't work at all w/o JS...
It was enough to cancel my card...
NGWave - Fast Sound Editor for Windows
Might be useful: user-agent masquerading in a simple to use toolbar for mozilla
python -c "x='python -c %sx=%s; print x%%(chr(34),repr(x),chr(34))%s'; print x%(chr(34),repr(x),chr(34))"