Introducing IE=EmulateIE7

re: Introducing IE=EmulateIE7

Void — Wed, 11 Jun 2008 04:01:05 GMT

This would be a good approach to keep the old web from breaking apart.

re: Introducing IE=EmulateIE7

SiSL — Wed, 11 Jun 2008 04:06:08 GMT

Does it currently work with IE8b1?

re: Introducing IE=EmulateIE7

Ready? — Wed, 11 Jun 2008 04:09:29 GMT

The question is, will IE8 be ready for the web?

re: Introducing IE=EmulateIE7

SiSL — Wed, 11 Jun 2008 04:24:39 GMT

Sorry my bad... Missed the hotfix part

re: Introducing IE=EmulateIE7

Wraith Daquell — Wed, 11 Jun 2008 04:54:40 GMT

Not to sound like a ticking clock, but once again I applaud the IE team. Before, although I was excited, it did seem that Microsoft was having trouble listening to the public and understanding what we need. However, now it seems that you are adding practical things. Two thumbs up!

re: Introducing IE=EmulateIE7

Jerome Lapointe — Wed, 11 Jun 2008 05:47:57 GMT

Well you have my support and I will definitely push for my company to let me update our website to run on IE8 as the default rendering and take advantage of the supported standards.

IE8 unterstützt (mehr) Webstandards standardmäßig: Danke Opera! Danke EU! und -okay- Danke MS!

patch-info.de — Wed, 11 Jun 2008 06:24:06 GMT

Microsoft hat sich vor der Veröffentlichung einer Beta-Version des kommenden Internet Explorer 8 (IE8) nun doch (einigermaßen überraschend) dazu entschlossen, die ggü. IE6 und IE7 standardkompatiblere Darstellung von Webinhalten standardmäßig zu verwende

re: Introducing IE=EmulateIE7

Henry — Wed, 11 Jun 2008 07:09:55 GMT

"The preferred response to this call to action is to ..."

NO, NO, NO, NO, NO, NO!

The PREFERRRED response to this CALL TO ACTION is for Microsoft [MSFT] to explain what is going to be fixed in BETA 2 (both regressions, and legacy IE bug fixes) so that WE can correctly handle the Beta 2 version (supporting IE8Beta1 is like trying to juggle chainsaws while keeping your site held together with duct tape)

Will .getElementById() trully be fixed in IE8 Beta 2?! (wasn't in Beta 1!) or do we still need to route all versions of IE through an overwritten version of this function that correctly returns the right element?

Will .setAttribute() trully be fixed in IE8 Beta 2?! (wasn't in Beta 1!) or do we still need to route IE8 through magical hoops to set event handlers and some other cAmEl CaSe IE attributes?

Will filter:alpha() be fixed?! I don't want my 75% opaque elements rendering at 0% opacity because of regressions in IE rendering! Let us know if it will be fixed or not, so we can remove all occurrences in IE8 if it will still be broken, or leave them in if this regression will be fixed.

What happened to being open with the developers?! This seems like darn near critical info, yet you hold back as if the world will crumble if this information is released. What gives?

Henry

re: Introducing IE=EmulateIE7

Henry — Wed, 11 Jun 2008 07:15:47 GMT

Oh, and lets not forget:

valign on table cells (td valign="top", td valign="bottom")

Will this be fixed in IE8 Beta 2 or not?

There ARE NO WORKAROUNDS for this bug currently so I certainly hope that this is being fixed.

Again, you need to advise us of the status on this regression bug if you want ANYONE to support IE8 without resorting to sending bogus headers and holding back the Web.

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!

re: NO, NO, NO, NO, NO, NO!

Ferd Burford — Wed, 11 Jun 2008 07:50:30 GMT

@Henry,

NO, NO, NO, NO, NO, NO!

DON'T continually redesign your websites to ANY -unique- Internet Explorer BETA attributes.

Just take note and prepare for finalized response. ;)

re: Introducing IE=EmulateIE7

mocax — Wed, 11 Jun 2008 08:24:57 GMT

I think developers are confused by the statement "getting yours sites ready"

Some I know are already writing workarounds for bugs in beta 1. I'm sure these workarounds will break when the bugs are fixed.

Émuler Internet Explorer 7 sous Internet Explorer 8 quel que soit le mode de rendu

Blog - Britoweb — Wed, 11 Jun 2008 11:27:12 GMT

Afin que les pages Web censées utiliser le mode Quirks puissent toujours l'utiliser, une nouvelle valeur de l'en-tête X-UA-Compatible a été créée, appelée IE=EmulateIE7.

OPACITY! OPACITY! OPACITY! OPACITY!

rc — Wed, 11 Jun 2008 12:03:50 GMT

OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY! OPACITY!

re: Introducing IE=EmulateIE7

peter — Wed, 11 Jun 2008 12:12:10 GMT

I am from belgium, the capital of europe.we don't have referendum, and we said no, but they don't care and choice for use..

please, say no to the europe

cordialy,

re: Introducing IE=EmulateIE7

Mike Dimmick — Wed, 11 Jun 2008 15:24:07 GMT

The point of "X-UA-Compatible: IE=7" is for the page to render however IE 7.0 does. I think IE 8.0 should go into an IE7-compatible quirks mode when it encounters a DOCTYPE that would have put IE 7 in quirks mode, if X-UA-Compatible is also present.

In other words, I think you should remove IE=EmulateIE7 and just make IE=7 work like the new behaviour specified for IE=EmulateIE7, or (given you have now instructed web developers to change their declaration again), support both as synonyms.

I just don't see the point of forcing "quirks mode" pages into IE7 standards mode if IE7 would not have done so. It's more likely to break pages than not. As described, IE=7 with an old or no DOCTYPE will be an entirely new mode for IE8 only - you're providing an option to be compatible with nothing.

I still think opting in to newer standards mode was a better solution, but don't overcomplicate it.

re: Introducing IE=EmulateIE7

Dave H — Wed, 11 Jun 2008 15:43:09 GMT

So if I have a page with no DOCTYPE at all, and with no X-UA-Compatible meta tag or header, does it default to IE8 standards mode or quirks ("IE5") mode? Thanks.

re: Introducing IE=EmulateIE7

Brian LePore — Wed, 11 Jun 2008 16:19:24 GMT

@Dave,

No DOCTYPE, no meta tag or header = quirks mode. This post just addresses the situation where the meta tag/header was essentially incorrectly forcing a quirks mode page into IE7 standards mode.

@Mike,

I agree with your point. I see this as a consideration that MS just forgot to take into account with the first beta that they are correctly fixing in an update. Since this is still very much a beta product, I don't see why they couldn't have just updated the previous behavior. That said, having the option to do both ways isn't bad.

@peter,

What?

@rc,

I think MS has heard the call for opacity support enough that we're going to get it. If it's still not there by RC1 I'll be shocked.

@Henry,

Checking your sites in betas is fine, but hold off on the re-designs until IE8 reaches a release candidate point. You're going to drive yourself crazy for months doing otherwise. :)

@Microsoft,

Thank you for the response, and thank you for listening to feedback!

re: Introducing IE=EmulateIE7

Carlos — Wed, 11 Jun 2008 16:29:41 GMT

So we get a tag that will solve some of the display issues on websites that had to be hacked to display correctly on IE7 so that we can have time to work even more on websites, that are already working one way or another, so that they can work on this new browser? Can someone explain this one to me?

Thanks

re: Introducing IE=EmulateIE7

Mike — Wed, 11 Jun 2008 16:35:05 GMT

This is silly.

We all have our sites with a valid DOCTYPE already to get "standards" mode rendering. However we also know that up until IE8 the DOM is very broken in IE, just like the CSS, and whitespace in HTML in IE.

So we have hacks. Tons of them. Hacks to make our CSS work because IE doesn't support x or y. Hacks in JavaScript to deal with broken IE method implementations and just plain broken support... .innerHTML on a Select Element anyone? How about on a Table Element? Yeah, why would you ever want to swap out the content of an Element that is a CONTAINER!!!!!! But I digress.

As I see it right now, we all have to add the site-wide header on production code:

X-UA-Compatible: IE=EmulateIE7

Until IE8 RTM ships. That (according to the posts and comments on this blog) will be the only time that we will really have any clue what will be fixed in IE8.

Meanwhile, when IE8 RTM does ship, developers will need to remove the header on local development/test environments, and hash out exactly what has been fixed, fixed properly, and what has gone missing, is a regression, etc.

Then we get to modify all our hacks to suit IE8, run another test cycle, then re-release production code for IE8 in "IE8 standards mode".

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?!

As for Henry (vote++) those are the critical issues on everyones mind.

As for "OPACITY! OPACITY! OPACITY! OPACITY!", I agree!

I hope you won't accuse me of plagiarism, when I quote you:

INDEED!

re: Introducing IE=EmulateIE7

Michael — Wed, 11 Jun 2008 17:07:30 GMT

As far as IE8 goes I really hope that the team takes its time to produce a browser that comes close to rendering like all the modern browsers it is so far behind.

It really says something about how low IE has set the bar when people beg for the proprietry alpha opacity filter. Just how hard can it be to get css3 opacity working.

If the job is worth doing, do it right.

re: Introducing IE=EmulateIE7

SiSL — Wed, 11 Jun 2008 17:47:30 GMT

I'm still looking for anchors display:block and z-indexes so I don't have to make my future developments based on IE7 tho...

re: Introducing IE=EmulateIE7

Taku Madzikanda — Wed, 11 Jun 2008 18:12:26 GMT

I cannot seem to get facebook to work properly using IE8 Beta and would like to revert to IE7 on my vista machine, but cannot seem to be able to do this, does anyone have any advice in this regard?

re: Introducing IE=EmulateIE7

rfink53 — Wed, 11 Jun 2008 18:18:21 GMT

Sorry to be didactic about it, but as someone who has been very hands-on with IE8 from the day it was released, I'm concerned that this aspect of the versioning metatag was not thought through from day one.

I can't be unique, and I noticed immediately that having IE8 ignore doctypes - with "IE7" triggering standards and "IE5" triggering quirks was confusing and an invitation to trouble.

It makes me fearful about what kind of input you are getting in-house BEFORE the user community even becomes involved.

It's difficult, I know, but important that things be considered AT THE OUTSET from the perspective of the average web author/designer/developer/site manager, et al.

But that said, it's a real good thing you caught the problem and fixed it.

Hoping IE8 is a truly great release.

re: Introducing IE=EmulateIE7

Duluoz — Wed, 11 Jun 2008 19:26:31 GMT

The root of the problem is that Microsoft, from the start, has chosen to provide a quirks mode that allows for incorrect markup to be displayed while providing a strict mode that doesn't align closely with recommendations set by the W3C and other accessibilities groups but rather where implementations of an under funded develeopment team with a misguided philosophy that their innovation would be the pack leader.

re: Introducing IE=EmulateIE7

Web Standards — Wed, 11 Jun 2008 20:01:55 GMT

Had MS not wasted those 4-5 years between the release of IE6 and IE7 working on useless, proprietary crap like Silverlight and actually fixed their browser instead, web developers wouldn't have the massive amount of of headaches. Silverlight is the new vendor lock-in since web developers already rejected the non-standard behaviours of IE.

Instead of reinventing the wheel when there is better solutions like SVG which is widely supported and is a recommended W3C standard, Microsoft has continously undermined any hope for compatability. Hopefully the market will reject proprietary crap like Silverlight and teach Microsoft a good lesson. Also another billion dollar fine from EU won't hurt either.

What's the point of IE=7?

Dan Fabulich — Wed, 11 Jun 2008 20:44:44 GMT

Wouldn't it be better to just make "IE=7" emulate IE7? What sort of person would declare "IE=7" but benefit from rendering the page differently from IE7?

re: Introducing IE=EmulateIE7

Frank Grimes — Wed, 11 Jun 2008 20:47:02 GMT

@Web Standards,

Yes, because it was the IE Team who were working on Silverlight and all that other 'proprietary crap'.

re: Introducing IE=EmulateIE7

Web Standards — Wed, 11 Jun 2008 21:00:58 GMT

@Frank Grimes,

You didn't see what Dean, GM of IE Team said at MIX 08? He said they were working on Silverlight and WPF/E during those years. Straight from the horses mouth, you can watch the video of the event if you don't believe me.

re: Introducing IE=EmulateIE7

Stifu — Wed, 11 Jun 2008 21:03:08 GMT

I'd like to add my vote to the drop the current IE7 mode, and replace it with the EmulateIE7 one.

That was the first thing that crossed my mind when reading this post...

re: Introducing IE=EmulateIE7

Web Standards — Wed, 11 Jun 2008 21:09:55 GMT

Also, they surely weren't working on fixing IE's problems, even Paul Thurott has a good writeup on it.

http://www.winsupersite.com/reviews/ie8_beta1.asp

"But as competition dropped off, so did Microsoft's competitive zeal. IE 5.x and 6 were minor functional upgrades, after which Microsoft essentially halted IE development and pondered dropping the product as an ongoing concern."

"So Microsoft reinstated the IE team"

IE8 will be another worthless, half-hearted release while they finish up proprietary Silverlight 2, again trying to reinvent the wheel.

Miguel de Icaza may be stupid enough to work on Moonlight for them for the Linux platform, but reinventing the wheel when there's widely supported standards is plain dumb no matter what.

re: Introducing IE=EmulateIE7

Anonymous — Wed, 11 Jun 2008 21:21:54 GMT

Well, from reading these comments one would come to the inevitable conclusion that the web developer community is populated largely by jerks. I just want MS to know that I, for one (apparently) appreciate the effort they are putting into the new release. IE is far from perfect, but it appears that it is at least moving in a good direction. Keep it up MS and please don't pay too much attention to some of these people with whom I am ashamed to be associated.

re: Introducing IE=EmulateIE7

Freedom — Wed, 11 Jun 2008 21:32:41 GMT

http://arstechnica.com/news.ars/post/20080610-commissioner-disses-microsoft-open-standardssmart-business.html

"Standards are clearly more important than ever. They often facilitate economies of scale but their real impact on technology markets is with interoperability," said Kroes. "I know a smart business decision when I see one—choosing open standards is a very smart business decision indeed."

Choose open web standards, say no to proprietary vendor lock-in.

re: Introducing IE=EmulateIE7

Andrey Moraru — Wed, 11 Jun 2008 22:26:49 GMT

Nice meta tag, because I doubt that many webmasters will be fixing their sites for IE8.

Interesting Finds: 2008.06.12

gOODiDEA — Thu, 12 Jun 2008 02:40:50 GMT

WebIntroducingIE=EmulateIE7Microsoft.comOperationsPerformanceAnalysisofIIS7.0/WindowsServ...

Interesting Finds: 2008.06.12

gOODiDEA.NET — Thu, 12 Jun 2008 02:42:03 GMT

Web Introducing IE=EmulateIE7 Microsoft.com Operations Performance Analysis of IIS 7.0/Windows Server

re: Opacity

Scott Dickens [MSFT] — Thu, 12 Jun 2008 02:52:35 GMT

@henry

@rc

@Mike

I don't want to go too far away from the topic of the top-level blog post, but I can quickly address the opacity question.

Opacity support in IE is provided via filters. The work to enable filters in the new IE8 layout engine unfortunately did not make the Beta 1 release. However, work on the feature set is currently underway and filters are still planned for inclusion in the upcoming Beta 2 release.

There was a bug that tracked the opacity issue filed via connect.microsoft.com site. Unfortunately, it was resolved as "by design", which only led to more confusion. My only explanation for why the reported bug was resolved as such was that whoever resolved it understood the story only for Beta 1 - the feature set was indeed "by design" missing in that release. Sorry for the confusion this has caused. Perhaps a better resolution would have been “fixed in later build” where “later build” meant before IE8 Beta 2.

re: Opacity

Brandan Lennox — Thu, 12 Jun 2008 05:39:12 GMT

@Scott Dickens [MSFT]

Would you mind blogging this so that (perhaps) folks will stop mentioning it?

re: Introducing IE=EmulateIE7

Glen — Thu, 12 Jun 2008 06:03:55 GMT

"Nice meta tag, because I doubt that many webmasters will be fixing their sites for IE8."

Some people don't have time because they're buried in projects. Plus when IE 8 comes out we'll still have to support IE 6 and 7. Kind of wish sometimes Windows 9x/ME came with some sort of decade kill-switch to force people to move to something modern.

"The root of the problem is that Microsoft, from the start, has chosen to provide a quirks mode"

The world was a different place when that decision was made. http://www.ericmeyeroncss.com/bonus/render-mode.html explains why it came into existence. The Gecko (Mozilla Firefox) and Presto (Opera) engines also have a "quirks mode".

re: Introducing IE=EmulateIE7

Ben 'Cerbera' Millard — Thu, 12 Jun 2008 11:11:54 GMT

As Dan Fabulich points out, the proposed behaviour for IE=EmulateIE7 is what IE=7 should do. This would make IE=EmulateIE7 redundant so it should never be introduced. This would simplify version targeting, which is complicated and troublesome enough already.

Ensuring the DOCTYPE switch works as it would in the targeted IE version is a no-brainer, isn't it?

I wish IE7 had never happened. The world will need to wait from IE6 to IE8 to get a properly standards compliant browser from Microsoft. IE7's incomplete rendering changes were an unnecessary complication during this time. It will continue our pain for some years yet.

re: Introducing IE=EmulateIE7

Chris — Fri, 13 Jun 2008 00:05:52 GMT

Scott, thanks for the update on opacity. As Brandon mentioned, it's probably a good idea to give that news its own blog post so that people will shut up about it :)

re: Introducing IE=EmulateIE7

Not a good idea — Sat, 14 Jun 2008 09:43:47 GMT

When will Microsoft do a browser that can really be standards compliant without adding their own non-standard functions. It is not a surprise that this yet another change requires action from many people. Can't Microsoft just make an automatic functionality inside the browser to fall into IE7EMULATION mode? Or add this text in the bar "This page may not display correctly? Do you want to use emulation?". It would be same as for popups. Easy way for webdesigners and webmasters to keep their running without issues. ==Less work for MANY PEOPLE! Thank you!

re: Introducing IE=EmulateIE7

Jeroi — Sat, 14 Jun 2008 23:15:59 GMT

I hope truly, that all the HTML and CSS standarts displaying bugs will be fixed atlast for the IE8. IE7 did not do with those anything, so the IE7 was more like IE6 with new GUI. So I think that IE8 will only be great if those bugs are fixed, so most web coders can make html+css sites work atlast with IE also, like Firefox and Opera does.

re: Introducing IE=EmulateIE7

AndresVia — Mon, 16 Jun 2008 02:14:19 GMT

Will IE9, still have the “IE=EmulateIE7” tag? I don't see the point in this "feature".

re: Introducing IE=EmulateIE7

Frymaster — Mon, 16 Jun 2008 16:45:49 GMT

"When will Microsoft do a browser that can really be standards compliant without adding their own non-standard functions."

I don't know a single _fully_ standards compliant browser. Perhaps you can enlighten me?

(I have heard of serveral with better compliance than IE7; perhaps this is what you mean? Equating them to absolute compliance is inviting the browser mess of the 90s to happen again)

Also, most browsers, in addition to whatever standard features they may have, include their own non-standard extensions.

"It is not a surprise that this yet another change requires action from many people. Can't Microsoft just make an automatic functionality inside the browser to fall into IE7EMULATION mode?"

At the moment there IE7 has quirksmode ("ie5") for the geocities element ;) There is the rendering engine used in ie7, which is ludicrously better than quirksmode but not perfect by a long shot. quirksmode is forced if the browser detects that the webpage is an uncompliant steaming pile of poo; otherwise it uses its own engine and tries to do the best it can.

IE8's best will be better, but some sites written to account for IE7's idiosyncrasies will therefor not render properly. Given the criteria for IE7 trying its best (the source data is standards compliant), how would you algorithmatically choose between ie7 and ie8 rendering?

Note the change in IE8 Beta 2 (or sooner)

Out Of The Box — Tue, 17 Jun 2008 02:39:34 GMT

On the IE Blog , they announced a slight change with the META Tag. I'm included an excerpt here: In IE8

IE=EmulateIE7 Doesn't Work

Clinton Gallagher — Tue, 17 Jun 2008 06:04:08 GMT

IE=EmulateIE7 does not work in a MasterPage head element when viewed using IE8.0.6001.17184 --but-- the same release of IE8 will display the content when using the Emulate IE7 button.

IE7 different on XP Pro and Vista SP1?

Clinton Gallagher — Tue, 17 Jun 2008 06:09:43 GMT

The exact same website being developed will display fine on XP Pro but is FUBAR when viewed on Vista SP1.

//XP Pro SP2

IE7.0.5730.11

//Vista SP1

IE7.0.6000.1800

This is really confusing and I see no other mention of this anomaly elsewhere. How can it just be me?

Quick Browser News

QuirksBlog — Tue, 17 Jun 2008 12:56:27 GMT

Sometimes browser vendors are appallingly insensitive. Despite my clear announcement that I’d be on holiday for two weeks, all four vendors saw fit to release major updates or important news items exactly in that period. Now I have to scramble to

re: Introducing IE=EmulateIE7

Tino Zijdel — Wed, 18 Jun 2008 02:57:03 GMT

So basically you are forcing other browser-vendors to implement this new kind of rendermode-switching else all documents that have X-UA-Compatible IE=IE7(+) or IE=edge but fail to provide a suitable doctype will render in standards compliant mode in IE, but in quirksmode in other browsers. Nice going...

If this was just an oversight than I trust you will revert this new 'switch' and make the X-UA-Compatible not override the conditions that will force quirksmode in current browsers.

re: Introducing IE=EmulateIE7

Anthony — Wed, 18 Jun 2008 03:28:36 GMT

@Clinton Gallagher

Yeah this is such a pain. Why doesn't this tag work with ASP.NET MasterPages. Do IE developers code inside a box?

Fix this or this whole project is a joke so far in terms of Microsoft being compatible with itself.

re: Introducing IE=EmulateIE7

Seymour Cakes — Wed, 18 Jun 2008 09:18:44 GMT

Remember IE3?

Everyone was skipping the built-in IE3 with Netscape. Heck that was the first thing most ppl do when they get online.

I think we need to stop paying attention to IE and start working to make web sites compatible with Firefox (particularly FF3).

re: Introducing IE=EmulateIE7

Joe Chung — Wed, 18 Jun 2008 12:40:15 GMT

IE=EmulateIE7 works fine on an ASP.NET master page. Make sure that it is getting rendered before any LINK[rel="stylesheet"] or STYLE elements.

Getting ready for IE8

andyBlog [andy britcliffe] — Wed, 18 Jun 2008 15:14:05 GMT

With BillG announcing IE8 Beta 2's arrival in August Jefferson has a great post on the IE Blog explaining

re: Introducing IE=EmulateIE7

Dave — Wed, 18 Jun 2008 20:08:34 GMT

Hi,

Will the IE 8 render divs containing pics faster than it is actually.

re: Introducing IE=EmulateIE7

Anthony — Thu, 19 Jun 2008 02:03:42 GMT

@Joe Chung

Good looks man. Someone needs to document that for later. Thanks again.

re: Introducing IE=EmulateIE7

realtor — Thu, 19 Jun 2008 07:19:34 GMT

Great article, very informative. I have to learn a lot!

Sunteți pregătiți pentru IE8?

Weblogul lui Zoli — Fri, 20 Jun 2008 13:16:31 GMT

Nu ca utilizatori, ci ca deținători/dezvoltatori de situri web? Dacă nu ați facut-o deja, testați-vă

re: Introducing IE=EmulateIE7

Elizabeth — Fri, 20 Jun 2008 21:30:02 GMT

I'm not an Web developer nor an HTML expert. I designed and maintain a basic site for a small nonprofit using MS Publisher 2007.

Will there be automatic downloads from MS to update Publisher so that the site I already designed will be compatible with IE 8?

I have no idea about adding the coding you discussed. I just want the site I already developed to be viewable OK by those using IE 8 when the time comes. Any advice greatly appreciated.

re: Introducing IE=EmulateIE7

Ian Thomas — Sat, 21 Jun 2008 06:11:41 GMT

1. Rendering

In my few weeks of using IE8b1 before I removed it, the page rendering experience was abysmal. Sure, that may refect the coding of the pages that I browsed to.

I'm not sure what you're now recommending for simple usage.

If a page doesn't render well in IE8b1's normal mode, should the user click the IE7 Compatibility mode? Is this enhanced by the patches released since I removed IE8b1 on 3 June 2008? Does Quirks mode get activated in IE8 render mode, if the page headers are appropriate?

2. Page saving

IE7 was consistently bad at saving some web pages to disk. In fact, this page (blog post) will not save from IE7 in either MHTML or HTML save modes. In my brief weeks of using IE8b1, it was no better. Why is that? Are you not concerned about that? I really don't like to have Opera 9.5 installed (I also have Firefox 2.x - originally installed for the same reason: IE just won't save some web pages to disk).

Web siteniz Internet Explorer 8'de düzgün görüntülenmeyebilir...

Aldığım notlar: .NET, VS.NET ve IIS... — Mon, 11 Aug 2008 17:58:09 GMT

Şu an Beta 1’i yayınlanmış olan Internet Explorer 8, standartları (HTML, JavaScript, vs.) daha sıkı şekilde

Web siteniz Internet Explorer 8'de düzgün görüntülenemeyebilir...

Aldığım notlar: .NET, VS.NET ve IIS... — Mon, 11 Aug 2008 17:59:30 GMT

Şu an Beta 1’i yayınlanmış olan Internet Explorer 8, standartları (HTML, JavaScript, vs.) daha sıkı şekilde

Web siteniz Internet Explorer 8'de düzgün görüntülenemeyebilir...

Aldığım notlar: .NET, VS.NET ve IIS... — Mon, 11 Aug 2008 18:00:26 GMT

Şu an Beta 1’i yayınlanmış olan Internet Explorer 8, standartları (HTML, JavaScript, vs.) daha sıkı şekilde

Easy Steps to Get your Web Site to Support IE8 in 5Mins

Thu, 14 Aug 2008 01:56:19 GMT

Put simply, IE8 running in standard rendering mode will not display sites created to support IE7 very

Introducing Compatibility View

IEBlog — Wed, 27 Aug 2008 22:12:01 GMT

At the start of the Internet Explorer 8 project we made a commitment to great website compatibility.

Apache httpd configuration for IE7 standard mode rendering in IE8

Hanu Kommalapati's blog — Thu, 28 Aug 2008 15:36:33 GMT

(Note: The following instructions are for information purpose only and correspond to Apache 2.2 on Windows.

Developer Tools in Internet Explorer 8 Beta 2

IEBlog — Thu, 04 Sep 2008 05:23:29 GMT

In March I wrote about the Developer Tools in Internet Explorer 8 Beta 1 and outlined three key benefits:

Developer Tools in Internet Explorer 8 Beta 2

No1 Microsoft Fan — Thu, 04 Sep 2008 14:56:12 GMT

In March I wrote about the Developer Tools in Internet Explorer 8 Beta 1 and outlined three key benefits

IE8 и совместимость: функция Compatibility View

Блог команды разработчиков Internet Explorer 8 — Tue, 21 Oct 2008 19:26:34 GMT

В самом начале проекта Internet Explorer 8 мы обещали обеспечить максимальную совместимость с веб-сайтами.

Compatibility View Improvements to come in IE8

IEBlog — Thu, 04 Dec 2008 03:34:55 GMT

The next public update of IE8 (for Windows Vista- and Windows XP-based operating systems as well as the

Грядущие изменения в режиме Compatibility View

Блог команды разработчиков Internet Explorer 8 — Thu, 25 Dec 2008 15:39:01 GMT

Следующее публичная версия IE8, которая будет доступна для пользователей Windows Vista, Windows XP и

차기 버전의 호환 표시 기능 개선

IE8 팀 블로그 — Fri, 13 Feb 2009 08:52:31 GMT

  업데이트 일자 : 2008 년 12 월 4 일 이 글은 Internet Explorer 개발 팀 블로그 (영어)의 번역 문서입니다. 이 글에 포함된 정보는 Internet

Just The Facts: Recap of Compatibility View

IEBlog — Tue, 17 Feb 2009 00:23:14 GMT

We’ve said a lot about our approach to website compatibility in general and the Compatibility View feature

Internet Explorer 8 Beta 2 개발자 도구

IE8 팀 블로그 — Fri, 27 Feb 2009 10:16:54 GMT

이 글은 Internet Explorer 개발 팀 블로그 (영어)의 번역 문서입니다. 이 글에 포함된 정보는 Internet Explorer 개발 팀 블로그 (영어)가 생성된 시점의

Site Compatibility and IE8

IEBlog — Fri, 13 Mar 2009 04:59:05 GMT

Reports of broken sites are an important part of the feedback the IE team receives from the community.

Being compatible with IE8

UK ISV Developer Evangelism Team — Thu, 19 Mar 2009 18:58:48 GMT

So IE8 has now made it to Release Candidate 1 (RC1), meaning that it will very shortly be in the hands

Being compatible with IE8

UK ISV Developer Evangelism Team — Thu, 19 Mar 2009 20:31:50 GMT

So IE8 has now been released, meaning that it will very shortly be in the hands of users for just browsing

IE8 X-UA-Compatible Rant

iBlog - Ilia Alshanetsky — Wed, 25 Mar 2009 15:44:44 GMT

A few days ago, Microsoft had done a low-key launch of IE8, which means you need to make your applications compatible with 3 differently broken version of IE ;-P. The biggest challenge IE8 poses is that it runs in "strict" mode by default, which coincide

호환 표시 기능(Compatibility View) 소개

IE8 팀 블로그 — Fri, 27 Mar 2009 08:53:12 GMT

    Internet Explorer 8 계획을 시작했을 때, 웹 사이트의 호환성을 유지하는 것을 공약으로 했습니다. 이 공약은 여전히 유효하고, Microsoft

Just The Facts: Recap of Compatibility View

Блог команды разработчиков Internet Explorer 8 — Mon, 06 Apr 2009 11:08:18 GMT

Еще раз к вопросу о Compatibility View: только факты Мы уже не раз говорили о нашем подходе к совместимости

KiNg.JiOnG — Wed, 08 Apr 2009 12:33:29 GMT

from:http://liupeng.us/Browers-Meta-Tag-X-UA-Compatible-ie8/

Walkthrough to Get Your Applications Ready for Windows 7

US ISV Developer Evangelism Team — Sun, 26 Apr 2009 01:13:13 GMT

The release candidate (RC) for Windows 7 is just around the corner. Dates for the Windows 7 RC were announced

Get your applications ready for Windows 7 – walkthrough (Part I)

ISV blog-voer — Tue, 28 Apr 2009 20:24:47 GMT

I was think if I should post this info knowing it’s an awful lot to read…. but it’s to important as the