RSSInternet Explorer 8 Beta 2 now scheduled for Q3
By Scott M. Fulton, III | Published May 27, 2008, 12:58 PM
The next builds for Microsoft's forthcoming Web browser generation may already be ready, but the company wants to give publishers some time to prepare, in case their Web sites end up looking somehow storm-damaged.
The next public preview of Microsoft's upcoming Web browser will be available in the third quarter of this year, according to a public blog post from a senior account manager in New Zealand named Nick Mackechnie yesterday morning.
The advance warning is apparently for a good reason: As promised, the next beta of Internet Explorer 8 -- and very likely the final release -- will render pages in "standards-compliant" mode by default. So Web sites whose rendering capabilities were geared more toward accuracy and compatibility with IE7, may not render as intended in IE8. So the company wants to give sites time to implement changes on their end that will reduce the shock for users once Beta 2 is released.
"Browsing with this default setting may cause content written for previous versions of Internet Explorer to display differently than intended," Mackechnie wrote. "This creates a call to action for site owners to ensure their content will continue to display seamlessly in Internet Explorer 8. As such, we have provided a meta-tag usable on a per-page or per-site level to maintain backwards compatibility with Internet Explorer 7. Adding this tag instructs Internet Explorer 8 to render content like it did in Internet Explorer 7, without requiring any additional changes."
The tag to which Mackechnie refers can be set either within a custom header in Internet Information Server 7, or within the <HEAD> element in individual Web pages. Specifically, it sets the X-UA-Compatible property to IE=EmulateIE7. It's a fairly simple tag to implement, and is explained in this page. (The latest test version of Apache's Web server, currently called Axis2, is working to add similar XML-based flexibility to its custom header processing.)
Recent builds of IE8 feature a prominent -- and some might say, ugly -- button that reads "Emulate IE7." Users noticing awkward-looking Web pages may use this button to see if the rendering problem is corrected, though the tag implementation Mackechnie suggests will allow sites to spare their users the trouble, and buy themselves a few months of extra time to follow Microsoft's lead towards standards compliance.
pnutts:
"how Microsoft is moving towards standards compliance"
*Moving*, perhaps, although I'm sure reluctantly. The noun used in the article was *lead*, not *move*.
Score: 0
|screenshots?
Score: 0
|The fact that they are giving developers time to catch up is a good thing. If IE8 was released today the uninformed user would think it was flawed because so many pages viewed in it would still be messed up. This is more to cover Microsoft's butt than anything else.
Score: 0
|Agreed. Even with this, however, MS will still be criticised for releasing a "flawed" browser.
Still, having used IE8 on my home PC for a while now, I can say that at least with beta 1 there aren't any features that I am relying on, or any features that make me say "I wish IE8 would be released sooner". IE7 will suffice for now.
Score: 0
|"... buy themselves a few months of extra time to follow Microsoft's lead towards standards compliance."
ROFLOL! When have M$ ever led towards standards compliance?
Score: 0
|"When have M$ ever led towards standards compliance?"
alanpalmer:
/. called and wants their post back.
I understand your question is rhetorical because it makes no sense. However, in the interest of accuracy, here's a quick response with one example.
If you visit the link below, you will find how Microsoft is moving towards standards compliance (or would you rather IE8 work like IE7)?
http://code.msdn.microso...ases.aspx?ReleaseId=568
Here's a link to IE8 CSS 2.1 testing:
http://blogs.msdn.com/ie...nd-css-2-1-testing.aspx
Score: 0
|Marvelous.
Just wish they'd release it earlier, personally.
Score: 0
|Isn't beta1 already rendering pages in "standards-compliant" mode by default? If so, I can't see how delaying a beta of a browser which is already out there is of any benefit to anyone. If they were delaying the first beta or the final it would make sense but the second beta..?
Score: 0
|