Microsoft warns Web site owners to prep for IE 8
Summary: Although Beta 2 of Internet Explorer (IE) 8 isn't due out until some time in August, Microsoft is cautioning Web site owners now that they need to be prepping now for possible problems the new, more standards-compliant browser may cause.
Although Beta 2 of Internet Explorer (IE) 8 isn't due out until some time in August, Microsoft is cautioning Web site owners now that they need to be prepping now for possible problems the new, more standards-compliant browser may cause.
As part of this week's IE June Security Update for IE8 Beta 1, Microsoft introduced a new tag, "IE+EmulateIE7" -- which it is counting on to head off some of the incompatibilities the company is anticipating could occur, based on feedback it received from IE 8 Beta 1 testers.
In a June 10 posting on the IE Blog, members of the IE team reminded site owners -- many of whom had designed their sites to display correctly in less-standards-compliant, prior versions of IE -- that they need to "get ready" for IE 8 so that their content will "continue to display seamlessly."
Microsoft decided earlier this year that it will make super-standards mode the default with IE 8. Super-standards mode is one of three modes which will be supported in IE 8. The other two are “quirks” mode, which will be compatible with current IE pages and applications, and a “standards” mode, which will be the same as what’s offered by IE 7 and “compatible with current content.”
(Microsoft originally planned to make the super-standards mode an opt-in choice and the IE 7 “standards” mode the default — claiming that by doing so, Microsoft would ensure better backwards-compatibility with existing Web sites and applications. But that decision angered those who felt Microsoft was shirking its commitment to make IE more standards-compliant.)
From the June 10 IE Blog post:
"In response to the great IE8 Beta 1 feedback we’ve received so far, we are introducing the 'IE=EmulateIE7' tag to address this problem. EmulateIE7 tells IE8 to display standards DOCTYPEs in IE7 Standards mode, and Quirks DOCTYPEs in Quirks mode. We believe this will be the preferred IE7 compatibility mode for most cases. Support for IE=EmulateIE7 is available now as part of the IE June Security Update for IE8 Beta 1. Installing this update will enable you to verify you’ve applied the EmulateIE7 tag to your site correctly."
Microsoft released a first beta of IE8 in March. Company officials have declined to say when the final version of IE 8 will ship.
Commentators were mixed in their responses to Microsoft's post, with some claiming the company was doing the right thing to ease the transition to a more standards-compliant IE 8. But others criticized Microsoft, claiming they need more information about which bugs the company plans to fix in IE 8 in order to design their sites and apps to continue to display seamlessly.
Commentator "Henry" weighed in:
"WE WANT to support IE8 fully, in the most standards way possible, but WE ABSOLUTELY NEED to know what IE will support in order for US to support it correctly!"
From poster "Mike":
"I'm okay with all of this, but gosh darn it would help a heck of a lot if there were say, like, uhm, some sort of guide as to what is going to be in IE8, kinda like a, uhm,... ROADMAP?!"
On June 11, the IE team posted about some new IT-specific features coming to IE 8 as of Beta 2, specifically the ability to slipstream IE 8 into a Vista (but not XP) image and the addition of new group-policy settings aimed at improving browser compatibility with apps and Web sites. Microsoft went public about these new features at Tech Ed 2008 this week.
What's your prediction as to what will happen when Microsoft finally rolls out IE 8? Will more users give it a try, due to its greater standards-compliancy? Will it "break the Web"? Will it slow Firefox's continued growth?
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
I expect all those who demanded standards compliance will...
As for the people requesting a road map there's already one out there: The standards. Follow them and you should be OK. Even better: Download IE 8 beta and start testing against it.
Again, MS has to ignore the catcalling
They should publicly ignore the catcalling.
TripleII
It's 50/50
It'll be interesting to see if you change the user agent of IE 8 to something else (e.g. Firefox), will the sites that break under straight IE 8 work.
Hacks aren't needed, use conditional comments instead.
Making all of my pages render correctly when IE7 was released was easy - just change a single line of HTML on the master template, and slight modifications to the CSS. The style sheet for IE7 was much shorter than the one for IE6, because IE7 rendered most stuff from my master CSS style sheet correctly. I imagine the experience will be similar with IE8.
Not just CSS
Very few websites should break.
Websites that already support standards will have no troubles with IE8. If your website doesn't support standards yet - it's time to change it.
More sites than you expect.........
Since a lot of these sites are necessary to access various functions, IE is on my system to address these broken sites.
Until ActiveX is buried, there will always be IE only sites.
Less sites than I care to visit.
Actually, will be a lot of sites because...
Plus there are still lots of sites that are IE only.
Wrong...
Not MY Intranet
Note Quite...
Take something as simple as Google Maps for example. In a way it is pretty much Ajax, its dynamically loaded content on the client side by javascript and such, and for the most part it works. You load up IE8, it looks like it went thru a blender, I do a lot of javascript development and in my testing IE8 breaks a crap load of sites that are interactive. And with most people going that direction now days, so will the likelyhood of breakage.
I suspect however that it may simply be because some of the javascript routines are checking for browsers, and see's internet explorer regardless of version and tries to apply fixes and hacks to IE8 that may not need to be applied, but either way I'm not impressed.
Firefox 3 on the other hand got released, and I'm still testing all the past sites I've done and I haven't found a breakage yet.
"Microsoft can't win this one"
The Firefox teams had to do a lot of work to get MS only (non standard) pages to display/be understood natively.
MS can't win this one because it is they that caused the mess in the first place. How about them compensating the countless thousands of lost hours making W3C stuff also work in IE?
Stop with the blaming
There was no standard for dynamic content when MS created IE4 and Netscape created NS4. Since none exist they both created their own but different standards. (could you imagine the mess we would be in today if NS4 with its "layers" was widely adopted?)
Standard bodies like W3C are part of the problem, they drag their heals when creating a standard; anyone still waiting for IEEE 802.11n (started 1/2004) wireless to become standard?
Corporate America (IE4's main reason for being) couldn't wait and was knee deep in IE 4/5 with their intranet sites when the W3C finalized their standard. At the same time the code from the intranet spread to internet where the rest of us picked it up and started doing the same.
It wasn't till 2002 when Mozilla released the Mozilla 1.0 browser and Firefox wasn't even a wet dream yet.
MS created what was needed for the time and there was no standard for it, we all used it and we all needed it, can you imagine if we had only static sites until the W3C was ready?
The internet would not be what it is today, the Mozilla Foundation would probably never have been formed and we would never have heard of Firefox except in a Clint Eastwood movie.
Too bad,
What a load of rubbish
Just having the first clue would help, like understanding the basis of free markets and competition as developmental drivers.
"Corporate America couldn't wait" Yeah, I see what planet you're from kiddo. Enjoy your spoon feed - it saves you thinking for yourself.
When's the next press release due?
RE: Stop with the blaming
Corporate America (IE4's main reason for being) couldn't wait and was knee deep in IE 4/5 with their intranet sites when the W3C finalized their standard. At the same time the code from the intranet spread to internet where the rest of us picked it up and started doing the same.
[/i]
What a load of uneducated roundup talk there.. the code of the intranet spread to internet? lol! what are you on about??
BTW, Mozilla originates from Netscape..
The IEEE has nothing to do with the IETF..
But Firefox was indeed a movie with Clint Eastwood in it.. at least you got that right :)
Here is the point...
would not be in this position now. To tell someone to, the
standards, is the roadmap is not helpful because, back to
first point. Plus, IE8 will be MORE standards compliant, does
mean one would need to know which standards it will comply
with.
compliance to what
I expect it to comply more with 'the' Web standard, W3C !
.