Forum Moderators: open
And now I read there's a security update coming for IE8, too.
Conditional comments not targeting IE8 are the easiest solution by far.
But It will be a blessing if Microsoft can get IE6 usage wiped away, just imagine the time saved around the world for not having to deal with *that* browser. IE7 is of course next in line.
It's only when IE8 sees the added stuff for IE6 and IE7 that it starts to act up.
That's what I was assuming, too, but I had a wake-up call. When I get this current case boiled down to its essence, I'll post about it. There are no IE conditionals involved.
Still, I'll be very happy to see IE6 fade away along with the corporate attitude that created it.
I was actually surprised at the relatively-high up-take on IE8 before this "forced upgrade" -- It seemed to be pretty strong, considering that Web users previously had to intentionally "go get it" from MS.
Equally surprising (to me) is that we haven't already seen a bunch of new threads here at WebmasterWorld about user complaints of sites not working with their freshly-installed IE8 browsers.
Jim
So far no IE8 so maybe this toolkit still works:
[microsoft.com...]
I'm wondering if Microsoft will finally start to fix bugs in IE8 aside of security issues and violated patents, cause they never fixed bugs in IE6 nor IE7 related to their very broken CSS implementations.
Till they do get rid of the legacy versions in the field and start to update the browser for bugs, from a CSS perspective, their browsers remain a block of concrete on our legs while trying to swim across the lake.
Equally surprising (to me) is that we haven't already seen a bunch of new threads here at WebmasterWorld about user complaints of sites not working with their freshly-installed IE8 browsers.
Hey, it's a proactive community jd! EVERYBODY downloaded beta and tested their sites earlier to ensure transition, right?