Ok, since so many people keep asking why Fluency Admin “does nothing when activated in Internet Explorer”, I thought I should post a nice graphic example of why I have it set up this way. I can guarantee that I would have had dozens more complaints if I had released it with broken IE support from the beginning…
On the left is a screen shot taken of Fluency running (or trying to) in Internet Explorer 6, quite clearly something is VERY wrong. And I have absolutely no idea how long (if its even worth it) it would take to fix. On the right is a screen shot taken of Fluency running in Internet Explorer 7. I was extremely surprised at how close it is to working correctly (since it was never tested in IE7), only really seems to be a few things out of alignment, which should be fixable.
What does this mean? Well, since IE7 is so close, I’ll see what I can do to get it working for the next release. All I need to do is find a different method of ‘hiding’ Fluency so that IE7 can see it, but IE6 can NOT.
