Linked by Thom Holwerda on Thu 4th Aug 2005 15:01 UTC, submitted by Tudy
Internet Explorer In a recent blog posting, Internet Explorer's lead program manager Chris Wilson revealed many of the technical improvements that Microsoft will add to IE 7.0 for its final release. Almost all the improvements are related to bugs in IE's implementation of CSS. Many of these bugs aren't fixed in the currently available IE 7.0 Beta release. Wilson's post raises some serious questions about IE 7.0.
Thread beginning with comment 13530
To read all comments associated with this story, please click here.
Backwards compatibility
by youknowmewell on Thu 4th Aug 2005 15:25 UTC
youknowmewell
Member since:
2005-07-08

It's a blessing and a curse. It makes developers both happy and unhappy at the same time.

I say that they should simply include proprietary DOCTYPE-like code to allow developers to simply tell the new IE7 to render as IE6. This would allow MS to fix the problems and at the same time allow developers a smoother transition. For developers that need or want the new goodies (later on at least), this will allow them to use them. For developers that need or want to keep the old code they already have, this helps them as well. Of course, there will be those people that will yell, "NO PROPRIETARY CODE!", but I think this is a good compromise for now.

Reply Score: 1

RE: Backwards compatibility
by on Thu 4th Aug 2005 15:55 in reply to "Backwards compatibility"
Member since:

Yes. Then they'd have to listen to complaints like "It's BLOATED!". Truelly a no win situation. Being #1 puts on handcuffs that #2 and 3 don't have to deal with.

Reply Parent Score: 0

RE: Backwards compatibility
by ma_d on Thu 4th Aug 2005 17:06 in reply to "Backwards compatibility"
ma_d Member since:
2005-06-29

That's a horrible idea. If the people with badly written websites do get around to fixing their sites we want them to fix them: Not add a line at the beginning indicating that it's bad code. There may be sites that don't work now, but that's fine: They'll have to fix them correctly for once. Yes, they'll complain about it. But they should have been complaining when they implemented it wrong to work around buggy IE rendering. Or when they implemented it wrong and someone noticed: Hey this only seems to work on one browser.

Here's another question: When will they be releasing and IE7 for Mac? At this point Mac is the only platform on which you can test against every major browser. Windows lacks khtml, Linux lacks IE, and Mac just has a one-step outdated IE (Mac still has IE 5.5 right?).

Reply Parent Score: 1

youknowmewell Member since:
2005-07-08

That's unrealistic and foolish in my opinion. The code would be a bandaid to fix things up temporarily, but eventually those people that use it would fix their site. It's unreasonable to force people to spend money and time fixing an artificial problem at someone else's will. Whilst I see room for compromise, you see only black and white. That's the sort of attitude most people hate. It's arrogant, unproductive, and unreasonable.

Reply Parent Score: 1

RE[2]: Backwards compatibility
by on Thu 4th Aug 2005 17:46 in reply to "RE: Backwards compatibility"
Member since:

Mac does not have IE 5.5; the latest version of IE on Mac is 5.2.3. More importantly, IE/Mac is not really comparable to IE/Win. The former uses the Tasman rendering engine, the latter uses Trident.

As for Microsoft releasing IE7 for Mac: don't count on it. MS has announced that they will not release any more versions of IE/Mac.

Reply Parent Score: 0

RE: Backwards compatibility
by Clinton on Thu 4th Aug 2005 19:22 in reply to "Backwards compatibility"
Clinton Member since:
2005-07-05

As a web developer, I completely disagree.

IE is a piece of garbage and needs to be thrown away. I don't care if doing so required me to rewrite every piece of code I've ever written. Throwing IE out is the only way to go.

Microsoft needs to properly support web standards (in particular CSS) and to retard their dumb tendency to put proprietary junk in their web browser.

A web browser should be like a phone. Add whatever features you want (tabs, gestures, Javascript debuggers, themes, DOM browsers, etc.) but the redering of a page should be standards-compliant across the board. If it isn't? Junk it!

Reply Parent Score: 2

youknowmewell Member since:
2005-07-08

Personally, I'd like to forget IE exists. But I realize there are web devs out there that can't do so. We must deal with the reality of the situation, and the reality is that web sites MUST work with IE, web devs can't ignore it.

Reply Parent Score: 1

RE[2]: Backwards compatibility
by CPUGuy on Thu 4th Aug 2005 21:07 in reply to "RE: Backwards compatibility"
CPUGuy Member since:
2005-07-06

They ARE supporting CSS!!!

How hard is this to understand?

Reply Parent Score: 1