Have you tried the WordPress Automatic Upgrade Plug-in? I’ve been using it since I can remember and it makes the upgrade process extremely painless (for me anyway).

My plan of attack is to rework queries to the server so less objects are on page at one time. I have about 350 objects, give or take a few and Internet Exploder can’t handle that many. I have pagination set up to only display about 30 to 40 at a time. But they are all there, just not visible. My thinking in this design was that user interaction would minimize server queries and thus reduce response time. Then, in each subset, the user could persist changes if they wanted to.

It actually works really well… in everything but IE. So now I’m going to look at redesigning the page to re-fetch objects as the user paginates through. This will reduce the number of objects, but increase the user response time and make the user experience slower, possibly much slower with much bigger load to our servers. I will make Restful, JSON queries to get the data to make it as fast as possible, but I still have to rework the object construction on the page, not to mention the Rest queries.

I don’t even care if IE ends up being doggy about it. It just has to work. I have no concerns about the other browsers and their associated user experience because I’ve seen that already and it was quite good.

I have to admit… it is extremely discouraging to not be working on cool, new stuff and customer requirements because I get to spin on Internet Exploder cruft for a few days.

Sidenote: Have you tried using the IE7 compatibility tag? It’s a stretch but perhaps telling the browser to render in IE7 compatibility mode might lessen the amount of issues you’re having with your web app. I hate the tag because it’s not standards compliant and I’m anal about my code, but it might be worth a try. Other than that I guess I would say try to float as little as possible. It seems like when you have a lot of floated elements involved, something is bound to go haywire.

Then I had someone pull it up with a Windows XP machine with Internet Exploder 8. Just crap! Nothing works and it looks like hell. Guess what? I get to redesign all of it. Why? Because Microshaft pushes rubbish to the masses and now we’re strung up with having to develop to its limitations. I wish I could send a bill to those quacks for costing my employer a ton of money and for what? NOTHING! Everyone suffers. The software will be less capable, the customer doesn’t get the best experience, my employer loses money, and the product costs more for less quality.

Everyone loses with Internet Exploder and it has always been that way throughout its life cycle. For what it’s worth, I appreciate this article. I needed to vent. I need to know there are other people out there who are as disgusted and hateful as I am to the losers over at Microshaft. If Microshaft would just go away *everyone*, users and developers alike, would be a whole lot better off. We could get on with making lives better, solving customer problems, making share holders some money, and giving less headaches to developers. We have enough to do without this utter nonsense.