How... CRAP!

A number of on-line stores and banks in the UK do this, and it's unforgivable. Not to mention the fact that they're missing out on revenue. These is absolutely no reason for locking users out of your site just 'cause they don't use Internet Bloody Explorer:

Marks & Spencer
Argos (who've been promising to update their site for months now).



  1. y'know.. by that title I wasn't too sure I wanted to read it (in case it was a tutorial)! I have to agree with you that websites (esp. corporate/professional websites) that build their functionality around only one version of a web browser is one thing, but locking you out is just plain wrong!!! Unless a business has ties with M$, as in (from a legal/contract standpoint) they only offer their services to M$-using customers or something like that, I can't forgive this level of "intranet"-minded development.Chris Toohey#
  2. One of the bank sites (NatWest) locks non-IE users out because of how their DHTML menu-ing system works, I discovered (spoofed the user agent in Mozilla). Now, there's just no need for that. It's plain laziness.Ben Poole#
  3. That's just wrong. I like DHTML menus as much as the next kid, but basing browser-compatability on them is unacceptable!Chris Toohey#
  4. Co-operative Bank's Java applet-based banking application doesn't work with the JRE that you need to use with Mozilla as a plug-in so it's effectively IE only. is fine though I still get some Mozilla bugs. Chris Melikian#

Comments on this post are now closed.


I’m a software architect / developer / general IT wrangler specialising in web, mobile web and middleware using things like node.js, Java, C#, PHP, HTML5 and more.

Best described as a simpleton, but kindly. You can read more here.