Developing for old browsers is (almost) a thing of the past
1–10 of 37 posts
Re: Developing for old browsers is (almost) a thing of the past
#2By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet.
This leaves them with only one option if they want support on a long-term supported browser, which is the recently shipped Firefox Enterprise Support Release.
Re: Developing for old browsers is (almost) a thing of the past
#3I think the title is a little bit misleading. The moment you can drop support for browser versions is pretty dependent on the requirements of your client, and your visitors. 7% for users with IE8 or lower is a pretty tech-savvy crowd, many developers might not have the luxury of dropping support for IE8 because many of their visitors still use that browser.
Re: Developing for old browsers is (almost) a thing of the past
#4By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet. This leaves them with only one option if they want support on a long-term supported browser, which is the recently shipped Firefox Enterprise Support Release.
Except there are no customers. It's a new product, and if you want to use it then you'll need an up to date browser. No-one is being cut off.
Re: Developing for old browsers is (almost) a thing of the past
#5I'm so sick of websites not even attempting to render in a browser not in their whitelist. Please give me a button that says "I understand the risks, but I want to try anyway."
Re: Developing for old browsers is (almost) a thing of the past
#6By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet. This leaves them with only one option if they want support on a long-term supported browser, which is the recently shipped Firefox Enterprise Support Release.
>>>By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet.
Nonsense.
Chrome and Firefox will both run on XP.
Re: Developing for old browsers is (almost) a thing of the past
#7By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet. This leaves them with only one option if they want support on a long-term supported browser, which is the recently shipped Firefox Enterprise Support Release.
Sounds like they simply want to remove as much legacy as possible in the new product. The old product will still work. They are "skating to where the the puck is going to be..." in a year or so.
Re: Developing for old browsers is (almost) a thing of the past
#8By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet. This leaves them with only one option if they want support on a long-term supported browser, which is the recently shipped Firefox Enterprise Support Release.
>>>By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet. Nonsense. Chrome and Firefox will both run on XP.
You'll notice the second sentence there, which talks about Firefox ESR as the only option if they want a long-term supported browser. Many large corporations will not switch to a browser which updates itself more often than they can easily test it against all of their internal apps.
Re: Developing for old browsers is (almost) a thing of the past
#9I'm so sick of websites not even attempting to render in a browser not in their whitelist. Please give me a button that says "I understand the risks, but I want to try anyway."
We don't do that. We only discriminate against browsers we know will have problems. Like IE6-8. So what we're running is actually a blacklist.
If you show up with a browser that's not one of the big four, we're just letting you in on your own accord.
I completely agree that whitelisting for browsers is bullshit.
Re: Developing for old browsers is (almost) a thing of the past
#10Earlier quoted context omitted.
>>>By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet. Nonsense. Chrome and Firefox will both run on XP.
You'll notice the second sentence there, which talks about Firefox ESR as the only option if they want a long-term supported browser. Many large corporations will not switch to a browser which updates itself more often than they can easily test it against all of their internal apps.
Is the Google Chrome Frame for IE an alternative option for such users?