Monday, December 26th, 2005

IE for Mac. Done. Thank god.

Category: IE

<p> We have been at a few clients that asked us for Ajax support on IE for Mac. You have to have a bit of a laugh with that bad boy. Unfortunately, some clients require support for this beast, and although “support” means different things at different places… (e.g. degrades so it is readable, vs. same experience) it was always a pain.

Now that Microsoft will stop supporting the beast in a few days, does it really matter? Will these policies be changed so we can move on? Can we now say “but hey, look. Microsoft support is done, so can’t we stop?”. I guess the main metric is the number of browsers coming into your application, and how inclusive you want to be. Microsoft’s announcement doesn’t directly effect that, unless it gets those old guys to upgrade, and if they haven’t done so by now?

IMPORTANT INFORMATION FOR MICROSOFT INTERNET EXPLORER FOR MAC USERS

In June 2003, the Microsoft Macintosh Business Unit announced that Internet Explorer for Mac would undergo no further development, and support would cease in 2005. In accordance with published support lifecycle policies, Microsoft will end support for Internet Explorer for Mac on December 31st, 2005, and will provide no further security or performance updates.

Additionally, as of January 31st, 2006, Internet Explorer for the Mac will no longer be available for download from Mactopia. It is recommended that Macintosh users migrate to more recent web browsing technologies such as Apple’s Safari.

Related Content:

Posted by Dion Almaer at 10:01 am
6 Comments

+++--
3.2 rating from 13 votes

6 Comments »

Comments feed

R.I.P

Comment by José Jeria — December 26, 2005

Digressing a bit from MSIE for Mac issue, how about building Ajax components with nothing more than good old JSP? Components, that can degrade very gracefully in case XHR or Javascript is not supported? They even work in Netscape 4! Check out this demo: http://www.superinterface.com/jspcontrols/tabcontrol/index.jsp

The tab panels in the demo are updated in-place using Ajax, if XHR is available. Turn Javascript off at any moment and try to change tabs again. Visually, nothing changes. In reality, components redirect to main index.jsp page. The best thing is, that index.jsp does not have to conform to any specific API or to include any specific tags.

This demo is much simpler: http://www.superinterface.com/jspcontrols/login-fragment-ajax/index.jsp It is showcased in the documentation, telling how to build component that degrades from Ajax mode to non-Ajax mode.

The goal of the Library is not to provide ready-made components, but to support a certain request/response lifecycle. This is just a JSP file, go in and change what you need.

This is just version 0.2, but it shows the idea how the Reloadable Page Fragment (RPF) pattern works.

Comment by Michael Jouravlev — December 26, 2005

Good riddance.

Comment by manchicken — December 27, 2005

[...] IE Mac is Dead [...]

Pingback by Ajaxian » Audible Ajax Episode 14: State of Ajax in Denmark — February 6, 2006

Very fitting I think: “God is the inner principle of all movement, the only identity which already fulfils and illuminates the universe. Everything is incorporated in this one principle, because it encloses infinity, it includes everything, and there is nothing that could be outside of it. ” Giordano Bruno

Comment by Tom in Cala Dor Palma de Mallorca — October 1, 2006

It’s been years now, and one of my client still wants support :)
Maybe it will never really die, but always live in the client’s hearts.

Comment by Sudhanshu — November 17, 2007

Leave a comment

You must be logged in to post a comment.