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.
YOU’RE GREAT
IExplorer 6 sucks. I forgot to support it since last year.
Great work
How do I use the Fluency in IE7? Thanks
People still use IE 6? Scary.
BTW, I love Fluency. Thank you! I’ve been putting off upgrading (ok, I still am) my WP due to my intense dislike of the new admin interface. You made it much more useful and friendlier for big monitors, too.
Looking forward to the new version!
*Adding an obligatory “why do people use IE anymore” nagging* :P
Oops, sent that reply before I saw your reply
I’ve been pretty happy with Conditional Comments. They’re solid in IE, and it saves an awful lot of hassle with user agent checking scripts, which need to be kept up to date and awful lot.
You could probably use a conditional comment to add something to the head of the admin screen if “ltIE7” saying that the user is using an outdated browser and that they should upgrade to IE7.
From the sounds of things your admin panel should work solidly in IE8, seeing as they’ve passed the Acid2 test now. Looks like IE is finally getting its act together, and in the not too distant future we won’t have the pain of having to sort out support for the antiquated IE6.
Full conditional comment instructions here
Thats one option, I was thinking more about checking the user agent, but both would probably have the same results anyway. And yes, in theory, I won’t need the @import since I won’t need it to “disable” IE anymore.
Should be simple enough - just echo conditional comment around line 12 of your plugin file. This will probably mean you won’t need to use an @import rule in wp-admin.css either.