I found a great list on the blog/news section for the ocPortal CMS, 10 IE compatibility problems that you might not have realised. While the post is related to ocPortal, the Internet Explorer compatibility issues likely will apply to any CMS viewed by the browser.

Over the year's ocProducts has maintained a private list of issues in different web browsers, and if there's one thing that is consistent it is that Internet Explorer has the majority of the problems. Sometimes they are bugs, but as you'll see from this list sometimes other browsers just do things better. I am writing this blog post not to bash Microsoft, but hopefully to provide some useful information to other web developers. Thankfully IE8 fixed a ton of problems, and I can't wait until we can ditch IE6 and IE7, but unfortunately this will inevitably be years away; never-the-less, as far as I am aware every problem here applies to IE8 as well as older versions.

I wouldn't be surprised if IE8 fixes some of the incompatibility issues that the author lists. I've been using IE8 at both home and work and have found the browser to be an improvement over IE6 and IE7. Nevertheless, I still prefer Firefox over Internet Explorer.

Now, the following rant isn't directed toward ocPortal but something that has hit a sore spot with me.

Although Firefox is my choice for Internet browsers, I do use Microsoft's Internet Explorer from time to time.  Yesterday, I installed the release candidate of Internet Explorer 8.

I can't say I'm a big fan of their "Web slice" approach as it feels like I'm ramming Google Desktop via RSS feeds down the browser's favorites bar.  Who know though, perhaps the slice approach will grow on me.  However, I am a big fan of Microsoft creating a more compliant and less buggy browser and IE8 seems to fit the bill.  If IE7 was a good step in the right direction then IE8 gets Microsoft's users pretty close to the destination.

Meanwhile, my rant to all the IE6 users.  I can't believe that about a third of Microsoft Windows users are still using IE6.  Shame on you if you are still using that insecure, buggy, and non-compliant browser.  Microsoft doesn't even want you to use that browser...and yet you're still stuck in the stone ages.  I have a theory that IE6 is symbolic of the problems of complacency at Microsoft and those companies/users that are still on that browser.  IE8 arriving on a modern Windows desktop near you and you're still on IE6?  Give me a break!

A recent blog post from Sarah Parez tries to answer some "want-to-know" questions on the upcoming Microsoft Office Web Applications.  With software as a service becoming more popular, Google has quickly become a competitor of Microsoft's Office Suite with its Google Docs.  Microsoft is aggressively fighting back by making its Office software available via the Web browser.

According to Perez's post, Microsoft's Office Web Applications will not only be available in Internet Explorer, but also Safari and Firefox.  Office Web will also be compatible on the Linux and Mac platforms.  Some of the specific answers Sarah Parez gives in her blog post:

Q: Do the Office Web Applications require Internet Explorer?

A: No! Office Web applications will work across multiple platforms and browsers including Safari and Firefox, too.

Q: Will the Office Web Applications work on the iPhone?

A: Yes, in the Safari web browser.

Q : Is Silverlight required in order to use the Office Web Applications?

A: No! Silverlight is not required. Using Silverlight will enhance the user experience, resulting in sharper images and improved rendering. Also, the Office Live Workspace has integrated Silverlight technology into the multi-file upload function for a better experience there, too.

Q: Will the Microsoft Office Web Applications work on Linux?

The single reason enterprises with Windows networks prefer Internet Explorer over Firefox and other browsers: Group Policy.

For those of you who might be new to Group Policy, here is a quick background. Let’s first assume you use an Active Directory environment to administer the computers in your corporate network. If that is the case, Group Policy provides a wide set of policy settings to manage IE8 after you have deployed it to your users' computers. These settings are locked down and cannot be changed by users, as they are always written to a secure tree in the registry.

Complete Story

Opinion: Microsoft has never said that they would drop support for Internet Explorer 6 (IE6) after the release of Windows XP Service Pack 3. However, I've often wondered if it would be to Microsoft's advantage, as well as beneficial to their customers, if they did drop the IE6 support. With Internet Explorer 7 (IE7) now the status quo for most non-Enterprise users of Windows and IE8 development underway, what better opportunity is there to end support for IE6 than now?

There is no question that Microsoft is supporting IE6 in the next service pack. Jane Maliouta, Microsoft's Deployment Project Manager for IE8, addressed IE6 support with XP SP3 in an IEBlog post on IE and Windows XP SP3.

XPSP3 will continue to ship with IE6 and contains a roll-up of the latest security updates for IE6. If you are still running Internet Explorer 6, then XPSP3 will be offered to you via Windows Update as a high priority update. You can safely install XPSP3 and will have an updated version of IE6 with all your personal preferences, such as home pages and favorites, still intact.

So the question remains, just how long does Microsoft plan to support this 7 year old browser? From as near as I can tell, support for Internet Explorer 6 is tied to the life cycle of the Windows XP operating system. Mainstream support for Windows XP is currently dated to end in April 14, 2009. So that means Internet Explorer 6 will have been on the desktop for more than eight years! While enterprises may take comfort that product support for Windows XP and IE6 has lasted so long, consumers and the rest of the world have since moved on with the changing world.

On Monday, Microsoft announced from their IEBlog that they were reversing their decision for how Internet Explorer 8 would be compatible with Web pages designed for Internet Explorer 7 as well as Internet standards. You may recall that earlier this year Microsoft announced that Internet Explorer 8 in "Standards Mode" would actually be rendering pages in Internet Explorer 7's "Standards Mode". If you really wanted to have IE8 follow the latest standards then you would need to insert a special <meta> tag to your pages.

While developers and users expressed opinions on both sides of the issue, I think it would be fair to say a large number of people were not happy with this decision. In my own comments, I stated that "this is just plain crazy" of a move by Microsoft as it held onto ideas of the past and not the present. In a March 3, 2008 post, Microsoft's Interoperability Principles and IE8, the IE team explains what you can expect with IE8 compatibility based on their changed decision.