Linked by Kroc Camen on Thu 25th Feb 2010 10:18 UTC
Permalink for comment 411203
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-01-18
The problem is less the standard CSS stuff, thats where IE6 can be layouted with conditional includes, hell starts with all dynamic web applications which have become modern... Also modern layouts do not scale well with all their transparencies and rounded corners, but you still can hack them in. Sheesh IE6 now is 9 years old and has had 2 revisions afterwards, get rid of it finally.
I am glad that Google is doing this.
Btw. the more dynamic content you get in the higher the effort becomes, my last count was 30% of additional implementation time to support IE6 in dynamic rich client interfaces on the ajax side of things. Given its marketshare hard to justify this anymore.
This data stems from a corporation I was involved in a project with which had lots of dynamic stuff in, and believe me, the CSS layout was our least concern regarding IE6 support. There were bigger issues in bugs, in IE6 having two separate rendering engines for different types of controls which are not properly synchronized against each other, performance issues on the dom tree, dom bugs which show at the fifth nesting layer of a dynamically replaced element etc...
A simply page supporting IE6 with a semi modern layout still is easy, but pulling off more complicated stuff is simply not justifyable anymore, hence Google is phasing out all its sites regarding IE6 I assume they have less than 5% of IE 6 users on their non search engine sites... It is not worthwhile anymore.
Ah yes and good luck getting bugfixes for all this stuff from Microsoft, the only bugfix to all this is IE7 which fixed about 5 bugs (like PNG transparency and the famous div bleedthrough bug (aka elements of the second native Windows based control rendering engine bleed through divs no matter which Z-Order they have)) closed a few loopholes for layout hacks and opened a can of worms of other bugs. The final bugfix for IE6 is ie8 the first bearable browser enginewise, Microsoft has delivered.
Edited 2010-02-26 16:48 UTC