IE 6 must die !#

6 Reasons Why IE6 Must Die

1. Lack of PNG Transparency Support
2. CSS Float + Margin / Padding Issues
3. Lack of CSS Pseudo-Class & Pseudo-Element Support
4. No Min-Height CSS Support
5. CSS Anchor Background Image Flicker
6. Crashing With Code

IE6 Must Die for the Web to Move On Show your support in twitter.
Tips: Make a redirect call in your header inside all of your templates:


Then create that nice page.
Trust me, your life will be better!

Trust me, your life will be better!

Not if my client hears that even one potential customer (or his aunt) couldn't get to his site. This might be a better idea.
http://www.smashingmagazine.com/2009/12/01/how-to-support-internet-explorer-and-still-be-cutting-edge/

It costs too much time for web designers/developer to make the patch or work around.
It's better to spend that precious time for the application itself.
If the permissive reason still stands, then the newer web technology will always has a huge weight in its feet.

MODx user's fact?
You will desperate using Revo on IE 6.

Not supporting IE6 on the Manager side makes the Manager much more capable and less bulky. That doesn’t change what the sites you build in MODx support on the front end. Heck you could support IE5 or NN4 if you so choose using Revo on the front end.

I loathe IE6, too, and can't wait to see it drop off the face of the planet. Unfortunately, it's still quite prevalent in many parts of the world. A site's traffic and business goals should determine whether or not IE6 support is done. I'm a fan of the Smashingmag approach Susan pointed out.

Quote from: rthrash at Dec 23, 2009, 08:03 AM

That doesn’t change what the sites you build in MODx support on the front end. Heck you could support IE5 or NN4 if you so choose using Revo on the front end.

Sad thing is Revo's installer can not even run on IE 6.
MODx is a back-end oriented content-management, right?
There is NO (even one!) "official" add-on for front-end management.
I mean management, not content/blogging system.

Quote from: rthrash at Dec 23, 2009, 08:03 AM

I loathe IE6, too, and can't wait to see it drop off the face of the planet. Unfortunately, it's still quite prevalent in many parts of the world. A site's traffic and business goals should determine whether or not IE6 support is done.

The IE 6 domination followed the Win XP's success story when it's started to be bundled inside the OS.
Worst story is even some parts of the word still use Win '98, right? (C'mon, guys... please use Linux if you can't afford XP).
Perhaps this w3schools.com 's "Web Statistics and Trends" can show the real game.
EDIT: Another better fact, Microsoft will end its support to IE6 on 13-Jul-2010.
While Microsoft tries to move on to campaign the IE 8, we stuck with this garbage.
Q: Why don't people change?
A: Because they just don't know that they SHOULD change and there ARE other options.

The web standard development is not their attention.
As a web technologist, we obligate to show the path, following these top 10 alexa rankings actions:
1. Google 2. Facebook 3. Yahoo 4. Youtube 5. Windows Live (i believe it is as same as MSN network below?)
6. Wikipedia 7. Blogger.com (same as google above?)
8. Baidu.com (Chinese search engine, perhaps doesn't effected much)
9. Microsoft Network (MSN) 10. yahoo.co.jp (same as yahoo?)

20. Even Microsoft itself.

You know what?
Wordpress has already have its plugin to annoy IE 6 users.

Quote from: rthrash at Dec 23, 2009, 08:03 AM

I'm a fan of the Smashingmag approach Susan pointed out.

You should start considering to put modxcms out of this swamp area, just like Revo declares its minimum requirement > PHP 5.1.x.

Ow, last but not least, found this better code :

I hate IE6 worse than getting a root canal, but let's face it, MODx puts no restrictions on your front-end design at all and probably won't ever even make recommendations on what MODx users should do in the front end.

Which browsers to support on a MODx site is always going to be up to the individual developer and there won't ever be an "official" policy on it.

The only real issue here, IMO, is what browsers modxcms.com will support (and, at present, I don't think it fully supports IE7).

While MODx is likely moving all the development path to Revolution, and keep the Evolution as the older branch support (I bet it's related with consideration on custom add-ons that built for Evo), there WILL no other way except dropping IE 6 support for Revo, and focusing on further web technology implementation (WEB2.0, AJAX, Javascript libraries, you name it).

We don't have to make it as "official", just take it as "recommendation".
How about that?

When I started designing, I refused to support IE6. I'm very open about it with my clients and haven't had a single complaint.

All the sites I do, I include the code from http://browser-update.org/

Lets users know that they need to update their browsers. Most people are more than happy to update, because they don't realise that browsers need updating like any other software.

good find.
this is also the redirecting: http://modxcms.com/forums/index.php/topic,51761.msg300768.html#msg300768