Die IE6, Die.
- Thread starter nvanprooyen
- Start date
To just edit your fairly accurate formula somewhat...
IE6/7/8 + CSS = Dick punch + Bollock stamp + A shit load of pinches of the back of upper arm by the tricep + Pulling a bird with bollocks
7 & 8 were vast improvements over 6.
8 completely supports CSS2 spec 100% so there's really nothing to complain about there.
Sadly, if you are not freelance, or working for yourself, you are not always able to dodge the bullet.
We are developing websites for international organisations and IE6 still has a sizeable chunk of users in that niche (Africa, developing countries, government organisations, non-government insitutions, etc...)
I know because I trudged through the statistics in the hopes of purging IE6 compatibility from our requirements.
No such luck, sadly.
But...
With even microsoft unwilling to support IE6 anymore (they officially announced that the new sharepoint will not have IE6 support), we are giving it the boot as soon as the current sites are done. :321:
:banana_sml::banana_sml::banana_sml::banana_sml::banana_sml::banana_sml::banana_sml::banana_sml::banana_sml::banana_sml::banana_sml:
::emp::
I see a world of difference in my site implementation between Firefox 3.5 and IE 8 (regardless of compatibility mode), mostly when it comes to CSS changes made via jQuery or using plugins. Needless to say, it all looks exactly as intended in Firefox 3.5. I'm far from a CSS expert so maybe Firefox is the offender but given IE's track record I'm laying the blame its feet for the time being.
That's what I'm talking about, no balls. Fuck IE6, tell those whom you develop for it's a pile. If you detect the version have it spit out a link to an upgrade or to a different browser. The idiots will get the point and stop using it.
The fact that people hide behind the excuse of "well there are still a bunch of fucktards that use it" is what's wrong. It could easily be wiped out in the matter of weeks (well maybe not but it could have been done by now).
That's exactly what i was geting at. CSS "interpretation" within any of MS's browsers is pretty loose. I lose count of the hours spent making something standards compliant work correctly in IE.
It's often the case that when viewed in any browser, apart from IE, most sites look perfect, but then has to be edited to fuck to get it to look similar in IE because IE doesn't implement the code in the same manner.
The reverse is also true, it's funny how many people move away from table based design only to test and build their site entirely within IE. It's obvious because you view that site within another browser and it's an absolute fucking mess. If people don't perform at least some cross browser checking, they should go back to working at McDonalds.
No compatibility mode, just strict XHTML.
Do you guys use a robust CSS reset (like Eric Meyer's or one from one of the other frameworks) in your work before you start coding?
I've yet to have any major issues with IE8. It looks exactly the same as FF. My problems (albeit small ones) tend to crop up in Safari, Chrome or Opera these days more than IE8.
Firefox, IE8, Safari, Chrome and Opera on one machine and a copy of IE6 on another... fucking joke
Yep - exactly. Using a global reset can help solve a LOT of problems. IE8 has been pretty good, IE7 the problems I run into are minimal but IE6 is just fucking awful.
Here's a good collection of css resets for those of you who aren't using that are interested - A Killer Collection of Global CSS Reset Styles ? Perishable Press
Firefox, IE8, Safari, Chrome and Opera on one machine and a copy of IE6 on another... fucking joke
I've been using IETester (for windows) for awhile so I can quickly check all the flavors on one machine. Free download here - My DebugBar | IETester / Browser Compatibility Check for Internet Explorer Versions from 5.5 to 8
