5 ms·
There is not supporting IE, and there is blocking IE. You are blocking IE - I know because I changed my user agent on my firefox browser and you blocked me, an
by ars 15y ago
There is not supporting IE, and there is blocking IE.
You are blocking IE - I know because I changed my user agent on my firefox browser and you blocked me, and that is not cool!
You don't even offer an option to let me try anyway!
Use feature detection if you must, ignore IE completely in testing if you wish, but do not actively block it or you are just as bad as those who only support IE.
- Achshar 15y agoI completely agree with you. But there may be some kind of security issues with IE. Some vulnerability to site's authentication system or something? not impossible, you see.
- kaolinite 15y agoThe security of the application should never rely on the client-side. If you're using Javascript or similar for authentication, you're doing it wrong.
- muyuu 15y agoThe user might get the wrong impression that he's being supported when he's not, and go ahead and buy some service that's not going to get support. At least a big warning is justified.
- jaffathecake 15y agoNot strictly true, most sites rely on the client's cross-domain policy for security. Without it, this site would be able to read your Gmail & facebook pages. If a useragent came out that had a major x-domain hole, I'd expect data-sensitive sites to block it. Not that IE fails in this way (and blocking IE in this case it wrong).
- kaolinite 15y ago+1. Valid point but this is a bit different to what I was referring to and is an insecurity in the browser rather than the application. Still, fair point. I was mainly referring to people validating input only on the client-side, redirecting people away from private parts of the site using JS or meta redirect (last year I had to maintain a site that used this), etc.
- nardi 15y agoCompletely disagree. There are two very major problems with this idea: 1. Your reputation suffers when users encounter issues while using the browser that you don't support. 2. The support cost of "letting users try anyway" is non-zero, and probably significant.
- deleted 15y ago[deleted]
- Kesty 15y agoYou still can put a big red sign with "This browser is not supported, here's why.", and let the user decide if they want to try it with IE just to see if is worth it the browser change.
- nardi 15y agoThat doesn't really fix either problem, IMO.
- Kesty 15y agoIE9 is actually not that bad, and IE 10 should hopefully be very good. As a developer my bigger problem with IE9 is that sometimes I forget to comment a console.log after testing. Their problem is that they want to be "pixel-perfect" across all browser. I get why, but as a User I don't really care as long as everything else works. And chance are that with IE9 and IE10 it will. I'm not a IE user, but when we stop supporting IE6 we put a big sign saying that if there were problems we won't fix them and to download a modern browser. But people still went to the site even if some divs were in crazy places because basic function they needed worked and maybe they hadn't the chance of upgrading their browser. If one of your client is once on another computer with only IE installed and doesn't have permission to install another browser, the fact that he can't use the website at all, is that a feature ?
- ludwigvan 15y agoYou may use log() instead of console.log() for that. See http://paulirish.com/2009/log-a-lightweight-wrapper-for-consolelog/ http://paulirish.com/2009/log-a-lightweight-wrapper-for-cons...
- Teapot 15y agoObvisouly, positive inclusive action is better than negative action. Properly detect IE without false-positives. <!--[if IE]> And inform IE-users a clear and simple explaination that IE is obsolete. And there's options for easy solutions to update to better browser. Links to the usual browser choices.