It won't work correctly. That is because it is broken. it was broken the minute it was released out the door. The fact that it was usable in a broken webbrowser does not mean that it was not broken.
[QUOTE=csswiz;3740235]It won't and therefore IE8 would break this intranet (and a lot of other sites and applications). You'll probably say that the business should update their site but as I've already pointed out, what are they likely to do? Stick with IE6 or update to IE8 and have to spend millions updating their intranet?[QUOTE=csswiz;3740235]
Since when was IE6 designed to be an application interface? If that's what they are using it for, then let them stick with it, but that does not mean that IE8 cannot be the web browser that it was intended to be.
If businesses can upgrade to IE8 safe in the knowledge that their applications will continue to work then we're much more likely to see older browsers fazed out which can only be a good thing for us as developers don't you think?
The phasing out of older web browsers is good, so long as the browser coming in is an improvement, and not merely a replacement for the sake of change. If IE8 will not render my standards compliant website in a standards-compliant way, then it is not an improvement.
It wouldn't be fixing the web. As I've already pointed out, it would break a lot of sites if it forced standards compliance and many users/businesses wouldn't upgrade as the perception would be that IE8 was a worse browser than IE6 (even though we obviously know better).
So it's the perception of better that is important, not actual advancement. I see. But I don't agree.
I don't really agree with the way their doing it but not sure what the solution is. What you're suggesting would be the ideal but it isn't going to happen as the end result would simply be that large businesses would decide to stick with IE6, leaving us with a user base of 20-30% of IE6 users as we currently have so we'd be in a worse of position than we are now as we'd simply have one extra rendering engine to support without the older browsers losing enough of a user base for us to drop it completely.
Even if a company needs to stay with IE6 for it's intranet, that does not mean that they cannot install Firefox or Opera or any other web browser for browsing the web.
At least with this trigger, us as developers will be able to use it to target a single version of IE which surely appeals more than the alternative?
No, it does not. What appeals to me would be a web browser that displays standards-compliant websites in a standards-compliant way. I don't buy the colateral damage argument, as anyone who depends on IE for an intranet can use a different browser for surfing the web.