81–90 of 167 posts
That means that by not supporting IE you don't get 70% of the market. Early adopters come and go, but "hockey stick" growth like the one Pinterest got? that comes from the mainstream market that uses IE and doesn't knows what Firefox is, and thinks that by Chrome you mean actual chrome...
But as I said IE is going down, and when it hits 50% in 2 years or less that will be the time to stop supporting IE.
IE market share has been going down for years, but it's still more or less 70% That means that by not supporting IE you don't get 70% of the market. Early adopters come and go, but "hockey stick" growth like the one Pinterest got? that comes from the mainstream market that uses IE and doesn't knows what Firefox is, and thinks that by Chrome you mean actual chrome... But as I said IE is going down, and when it hits 50…
> Originally, we feared that we'd receive a torrent of angry emails from avid IE users. In reality we've received exactly zero requests for IE support,
More generally, the "market share" depends very much on what you consider to be "the market". If your target audience are big companies stuck into MS support contracts then yes, IE market share is huge. If your target audience are mostly individuals with some basic knowledge on computers, they are almost certainly already using a sensible browser.
Earlier quoted context omitted.
If you rotate an iPad from portrait to landscape, for example, then the default behaviour in Safari is to show the same page layout as you had before, but scale it up to the new width. That's far from ideal if your site uses a responsive design that could adapt quite happily to use the extra width in a landscape orientation.
Can I just mention that at least on my phone, websites that "adapt" to landscape mode often bug the hell out of me. With my getting-old-eyesight, I often rotate to landscape mode to get bigger text so I can read it more easily. When a website goes "Oh look, more horizontal pixels, I'll shrink the middle column and add some nav on the left and ads on the right!"; I'll usually just hit [back] and move on to some other…
However, for most of our users, a zoomed single-column layout is going to be less useful than switching to two columns when in landscape mode on an iPad.
On an iPhone, you should see a single-column layout in either orientation using the design we're currently testing.
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.
Completely 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.
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.
Completely 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.
IE market share has been going down for years, but it's still more or less 70% That means that by not supporting IE you don't get 70% of the market. Early adopters come and go, but "hockey stick" growth like the one Pinterest got? that comes from the mainstream market that uses IE and doesn't knows what Firefox is, and thinks that by Chrome you mean actual chrome... But as I said IE is going down, and when it hits 50…
That doesn't seem to be an issue for them. From the article: > Originally, we feared that we'd receive a torrent of angry emails from avid IE users. In reality we've received exactly zero requests for IE support, More generally, the "market share" depends very much on what you consider to be "the market". If your target audience are big companies stuck into MS support contracts then yes, IE market share is huge. If y…
Just like IE users don't bother to find out which browser is the best they don't bother to email some unknown no-name startup they stumbled upon because the page didn't load.
And again I'm talking about a different and much bigger market than early adopters.
Earlier quoted context omitted.
Completely 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.
You 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.
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.
I 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.
Earlier quoted context omitted.
Is there something intrinsic to the WebKit versions on iOS products, or are your problems more general, i.e. learning how to support "limited" devices again (relatively small CPU, GPU, memory)? What is it about the iPad 1 & 2 that is giving you so many more problems compared to the iPad 3? I found I was spending way more time on IE bugs with Web app I recently did (~1000 users/month) than any other browser by far.
Hover states are a big one. Also making call-to-action targets bigger for the less precise pointing device (ie, your users' fat fingers). Making sure you use Flash fall-forwards with HTML5 video/audio available for iPad / non-flash devices. iPads and iPhones also have great support for CSS3 transforms (3D included with hardware acceleration), but some of the other "common" CSS3 and HTML5 technologies do bog down on t…
Can't you for the love of all that is binary do it the other way around? I hate it when sites push Flash on me on the desktop when there's a pure html version ready a user agent string away.
Earlier quoted context omitted.
You 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.
That doesn't really fix either problem, IMO.
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 ?