I feel happy, too…


…that someone got it.  Thanks, Hal – standards compliance and not breaking existing websites are, in fact, why I show up to work.


BTW, I will be at Web Directions North 08, MIX08, and (this just in) SXSW08.

Comments (104)

  1. thacker says:

    Thank you, Wilson.

    I have one simple dumbass question.

    If I use the suggested meta tag of:

    <code>meta http-equiv="X-UA-Compatible" content="IE=8"</code>

    it will only impact Internet Explorer, correct?

    Thank you.

  2. Robin says:

    I suppose we’re mostly worried that the solution you’ve come up with feels so obviously engineered to be perpetuated ad infinitum. This surely shouldn’t be an issue the next time around with IE9, because IE8 will get things correct. Right?

  3. Trevor says:

    First off, Happy Birthday!

    Now, why couldn’t you post the meta tag to the IE Blog?… that was like the ONLY thing in your post that I was looking for… (us up-to-date folks knew everything else)

    thanks,

    trevor

  4. cwilso says:

    @thacker: yes.

    @Robin: hope springs eternal.  :)  to be honest, I’ve argued on that side (one big breaking change), but the jury remains out.  New DOCTYPEs always help, though.

  5. Robin says:

    Well, new DOCTYPEs or MIME types (application/xhtml+xml, I’m looking at you).

  6. Thomas Tallyce says:

    I remain thoroughly unconvinced that the proposal is a sensible way forward. But the other news that major work has been done to improve the rendering with a new engine is really important and very promising. I can’t imagine how difficult it must have been to refactor the current engine! Thanks Chris for your ongoing advocacy within your team.

  7. thacker says:

    Damn it.  With this correction in IE8, it looks like I will be sending out to sea my frequently kicked Tom Hanks Coconut Haired Wilson Soccer Ball.  Which, incidentally, closely resembles another Wilson.  Damn it, again.  Looks, too, as though the hasLayout puns will need ditched.

    Wilson–

    The above were statements meant in jest.  Will miss the hasLayout puns, though.

    Thanks for the response and the hard work.

  8. Lionel says:

    Chris,

    There is one point you did not mention in your post: what will be the rules for the default rendering mode when X-UA-Compatible is not used.  Obviously it will be IE7-like for current web content, but, as noted by Robin, there is some latitude for other choices (e.g. it could be IE8-like, or even better, for pages with an HTML5 DOCTYPE, or an XHTML MIME type).  Has some decision been made about this possibility, or do you (all of the IE team) leave it open for the future?

    Thanks for the informative (although bound to start heated discussions) post, and (late) happy birthday!

  9. Lionel says:

    … Note that I’m not asking you whether IE8 will support XHTML (including MIME type), since nothing has been announced about it yet.  My question is about what has been decided for the first version that will support XHTML (whatever this version will be).

  10. Steve says:

    Are there any doctypes that do not require this new meta tag to render with the IE8 rendering engine?

  11. cwilso says:

    @Steve – sure.  Any unknown (i.e. not widely deployed) DOCTYPE.  HTML5, for example.

  12. Neal says:

    Hi Chris,

    I really respect the work you and your team have done with Internet Explorer 7. The fact that IE8 may pass the acid2 test is even better news. After reading the post on msdn this morning I sat down and thought over the whole process of IE selecting a rendering mode. I ended up coming to the same conclusion as Jeremy – http://adactio.com/journal/1402/.

    I think this is a really, really good idea but the thought of excluding the meta tag and having IE default to IE7 worries me.

    I think the default mode assuming a valid doctype is selected should be the latest and greatest version of IE. As long as you give web developers enough heads up, we can add the meta tag to our site before a new version of the browser comes out.

    As IE becomes more and more standards compliant there may even be a day where we won’t need the meta tag anymore.

  13. Diego says:

    So, wait, the rest of the browser crew doesn’t "gets it" and doesn’t wants to break existing websites? How fun…

    @tracker: In practice, millions of web pages will be implemented using the "IE=8" mode and firefox & others will have to mimic IE8. For other browser, it’s basically getting back to the 90’s.

    For IE it’s nice, of course, and I guess that’s all what matters for Microsoft. How typical…

    Pretending that a flag that it is intended to specify different behaviours for different browsers and then talking about caring about standards is /ironic/ at least. There’s a well know place for solving this and it’s the doctype, just request the W3C to decide something about this, a browser-specific flag is only going to hurt the web.

  14. Chris Ellis says:

    What web developers (At least Me) really want is a standards compliant browser.  Where I do not need to provide work-arounds in order to achieve the correct rendering.

    When the transition from IE6 -> IE7 happened we all had to modify our sites,  this was so we/I could leverage the enhanced rendering capabilities of IE7.  Then we used work-arounds to get IE6 to render correctly.

    Rather than buck this trend with half baked ideas, please consider why we/I would love a standards compliant browser.

    On a entirely different note:  

    What is IE’s / Mircosoft’s objection to making use of pre-existing web rendering kits like KDE-HTML / Webkit.  Surely as a whole community it would be better to invest all efforts into one defacto render kit than the current mess we have.  I understand you may need to swallow a lot of pride there.

  15. Alan Gresley says:

    Chris

    I will support you with conditional comments in the CSS on the CSS WG list.

    /* [IE standard] */

    A default IE8 standard mode with standard compliant code or the above comment in the CSS to force IE8 into standard mode with the presence of non standard selectors * html or *+html or IE conditional comments <!–[if IE]>.

    This won’t cause a repeat of the situation when IE7 came out and this doesn’t cause IE version lock-in which the new metas would.

  16. Franklin Tse says:

    What will the compatMode property (http://msdn2.microsoft.com/en-us/library/ms533687.aspx) return when the Super Standard Mode is activated?

  17. Dave says:

    Diego,

    As frustrated as I have been with designing sites that work in IE, I think you’ve being overly harsh on Microsoft here. If you read the IEBlog they make a really valid point – they shouldn’t break compatibility for the existing websites out there. When your software is ubiquitous as IE is, you can’t just tabula rasa for the next version – what’s more important, existing established websites that would need to spend thousands to fix things if they break when a new browser comes out, or supporting new sites designed by experienced developers who (mostly) know how to cater for quirks mode?

    I fully support the IE team in this and believe they’re doing the right thing. One meta tag isn’t perfect but it’s infinitely better than a thousand workarounds.

  18. Mitch 74 says:

    Hi Chris,

    I’m kind of double posting here as I did on IEblog – only because I’d like to say something that I think may make things better:

    – the meta switch is a good idea: it’s standards-compliant, useful, and accessible to both CSS and Javascript without having to parse a (conditional) comment, using normal syntax (CSS: meta[X-UA-Compatibility], Javascript getElementsByTagName(‘meta’).getAttribute…

    – making it default for all unknown doctypes is a given, I guess future ‘proper’ XHTML support will use it too

    However, considering that most content generators and editors usually use Transitional and/or Frameset doctypes, could you (the IE team) consider making Strict (X)HTML use the Super Standard mode too? Since Strict documents are supposed to be compatible with HTML 5, it would make sense.

    You’re right, users shouldn’t have to manually switch engines; however, you MUST absolutely notify users/developers when IE 8 uses IE 7 rendering, and mark it as an Error (equivalent to Jscript error) – otherwise we’ll all be stuck in the Dark Ages of Buggy rendering.

    One other helper: I understand that IE 5 must be supported until 2014 (as long as windows 2000 will be supported); but then, the IE 7/8 engine (not the UI!) should also be backported to Win 2000 and IE 6 buried.

    That would leave IE5 as ‘Quirks’ and IE 7/8+ s the ‘only’ engines to support. ‘You’ pulled the plug on IE 5.5, please do so on IE 6…

    I know, it’s not that easy.

  19. JS says:

    I really think it’s kind of silly that IE8 will require a proprietary tag in order to render webpages correctly.  I understand the goal of attempting to prevent existing pages from breaking, but it shouldn’t require that everyone who wants the correct standardized behavior follow proprietary non-standardized practices.

    I propose that the IE8 team consider a different approach:

    When the webpage has an appropriate DOCTYPE, the page will be rendered in the strictest standards mode that applies to the version specified in that DOCTYPE.

    When the webpage does not have an appropriate DOCTYPE, the page will be rendered using IE5 "quirks mode."

    Provide a couple mechanisms through which the webpage can declaratively request rendering using the quirks of any specific rendering engine through either META tags, DOCTYPE or HTTP headers.  Publish this mechanism well in advance as to permit existing sites to prepare for quirky rendering.

    I think this satisfies all requirements.  It does require existing sites to make a single change, which can probably be satisfied by simply adding a custom HTTP header to the configuration of the site.  All other sites would render as expected, and since no special settings would need to be put into place IE8 would pass the ACID2 test properly.

    I completely understand that MS doesn’t want to annoy customers by breaking websites, but really you should have thought of that over a decade ago.  The only way to make up for it is to do it right, by default.  Provide simple migration mechanisms if need be, but don’t require a custom tag for proper rendering.  You won’t pass ACID2, and neither the web developers nor the savvy web users will appreciate it.

  20. Lars says:

    While I’m not keen on the idea of introducing more special modes in any browser, I do realize that there might need to be something available the sake of backwards compatibility in IE8.

    Considering that, I’m willing to accept this meta tag/http header as a necessary evil, but only if the real standards mode is default. Let those who need the IE7-compatible "standards mode" add this one-line "fix" to their pages.

    I don’t believe that having to opt-in to real standards is going to work well for anyone in the long-term, not even for Microsoft.

  21. Anonymous says:

    1. For "Internet" and "Trusted sites" zone, do IE8 standards mode the default.

    2. For Intranet and Local Computer, keep old mode.

    3. Please ship a tool that automatically batch adds the tag to non-standards sites/pages.

    4. Please make IE8 at least on Windows 2000, if not 9x.

    If you don’t set IE8 standards mode as the default, mainstream sites today which STILL REFUSE to render properly in Opera and which work only in Firefox and IE will continue to do so. Please stop doing injustice to Opera.

  22. Ramon says:

    I think breaking the web would actually be a good thing. Give the people a meta-tag to switch IE8 back to IE6 and if it’s needed they’ll use that. But meanwhile they can see that IE8 has better standard support and perhaps alter their websites to cater for the ‘new’ web.

    This way the ‘old’ web will not linger on indefinetly as it will with the current proposal….

  23. Webdesign says:

    Thank you, Wilson.

    Are there any doctypes that do not require this new meta tag to render with the IE8 rendering engine?

  24. Greg says:

    Chris, could you or your team respond to the concerns raised here: http://weblogs.mozillazine.org/roc/archives/2008/01/post_2.html ?

    I was on board with the whole thing until I read that. Now I’m not so sure. Thoughts?

  25. Daniel says:

    Chris, please can you clarify something? You said that the IE8 engine will be used for HTML5 because its doctype is unknown. Once it becomes known will future versions of IE use the engine from the point at which it becomes known, or continue to use the latest engine?

    Also, do you have any idea how long will an old version of the IE engine continue to be supported?

  26. Chris says:

    Chris, just a short note.  If the rendering engine chosen is from an earlier version, please accept the conditional comments for that version too.  So, if IE8 defaults to IE7 standards mode rendering when no X-UA-Compatible value is present, accept the all the same conditional comments that IE7 would.

  27. Daniel says:

    Chris, sorry, but I didn’t yet understand what I’ve seen there just now.

    Is this all just an proposal yet or is this the thing thah will actually go into IE8?

  28. Daniel says:

    Oh, sorry another question as well.

    Will the Meta-Element be case insensitive and available in HTML-Syntax as well? <meta /> as shown in Gustavson’s article is XHTML.

  29. It must have been hard to cherry-pick someone who agreed out of the sheer volume (including web developers) who disagreed.

    The whole argument you present from the Microsoft perspective is already flawed. Existing websites have to be broken in order to even get them to work with Internet Explorer when trying to use just web standards. That’s the current baseline Microsoft very conveniently forgets time and time again in these discussions. So please don’t act all patronizing and holier than thou that you guys are doing this out of the good of your heart to enable the standards-compliant web. That argument is utter popcocky.

    The addition of the extra meta information reeks of a bad hack, plain and simple. Again, you guys failed.

    I will just make sure my websites have a disclaimer telling my visitors that if it looks strange in IE to blame Microsoft for not properly supporting standards. Too bad if I lose visitors that way, but it’s time for a change in tactics since it is obvious you guys will never listen.

    @Daniel: if it is in HTML it will automatically be case-insensitive. HTML’s DTD never cared for that due to the relevant SGML having been set to case-insensitive.

  30. Bill M. says:

    Was thinking about this as it relates to intranet sites and I propose the following method which may alleviate usage of the tag for normal Internet websites (I.e. those not in a business/intranet setting).

    Render in either quirks/standard based on the security zone of the site. If the site is an Intranet zone (Possibly Trusted Zone) site, then run in quirks mode to maintain backwards compat with older intranet apps regardless of the DocType setting of the Intranet app. Only if the proposed meta is present will IE not render intranet site in quirks mode. This does two things, ensures backwards compat with older sites and allows those building sites based on standards to ensure their site is viewed properly.

    Another option is to give businesses a local policy/GPO option for the new IE that SA’s can set on their clients to determine how the IE engine of that workstations will react depending on the security zone of the site IE is working with.

    Sites in the Internet zone will use Doctype only, rendering the most standards based when the standards DocType is used.

    Website owners can use Doctype for quirks mode… Sites using standards mode that really need quirks mode (site was built when what is now quirks was the IE standard) realistically should not affect my mom, as another site with similar content is just another click away.

    Those sites using standards mode, but really meaning today’s "Quirks" mode will likely not have updated enough content to keep me, or my mom, interested enough for very long.

    Just as MS will announce the end of support to a particular product because it becomes inferior, or the FCC says analog is going away on x/x/x, Microsoft has to come out and set a dead-line that all of the web sites stuck in the past have to get up to standard or they will no longer be supported.

    For example, give a 3 year window… something. You have to do this (eventually) or we will all be stuck in legacy hell forever.

    I appreciate your time and look forward to seeing what you will end up finally taking place. Good luck and take it easy! :)

    -Bill M

  31. Jeremy Keith says:

    Chris, have a great time at Web Directions North. I wish I could be there. But I’ll see you at South by Southwest. Let’s get together for a beer at the Great British Booze-up.

  32. cwilso says:

    @Jeremy Keith: you’re on.  I added the Booze-up to my Upcoming.

  33. Larry says:

    You haven’t indicated if IE8 is a Vista only browser, or an XP and up browser.

    I’d also like to indicate, that as I’m sure you’ve noticed, the left panel of this blog is rather-near impossible to read.

    I would suggest some CSS opacity? (cough, cough, IE-alpha) to layer the content above the image, or just add a whitewash to the image itself.

    I realize that the platform is more your gig, than web pages themselves, but ask yourself if you saw a house painted in plaid, would you consider hiring the painters to work on your next project?

  34. hAl says:

    Chris, could you guys make the default rendering engine (used when the user agent compatibility tag is not present) changeable in the advanced options of the browser (defaulted of course to the current IE7 rendering engine) ?

  35. Alan Gresley says:

    Hi Chris

    Advice……, take a nice long peaceful holiday far away to Australia or somewhere as remote and pleasant. It’s doing Molly a world of good.

    BTW, IE8 has just claimed 7th place by IE version for my site for January. Well done. Overall IE share is 34.03%. The biggest share of any browser is a massive 43.62% by Firefox 2.0.

    I may drive a hard line but in all respect, I am seeing in many places the IE teams’ commitment to make IE8 a much better browser.  Seeing all those rude comments over many years of blogs… Yes people may get frustrated but to show that side of human behavior is not right. Peace dude.

    Remember, go on a holiday.

  36. bilgi yarışması says:

    I realize that the platform is more your gig, than web pages themselves, but ask yourself if you saw a house painted in plaid, would you consider hiring the painters to work on your next project?

  37. Kravvitz says:

    What happens when IE9 comes out and someone wants IE9 to use its newest rendering engine but for IE8 to use the IE7 rendering engine?

  38. Caesar says:

    Simpler, better, solution : change the user-agent. Don’t identify as IE. Sites won’t know it’s IE, so they’ll send it standards-based code without trying to cater for old bugs. Problem solved.

    If you think it’s necesary, you could still suport a method (such as this meta tag) for sites to request the use of an old engine. Just make ‘edge’ the default. PLEASE?

  39. Andrew Sayers says:

    I hope I’m not too late to join this party (if I am, see you next post ;).  Anyway, here’s my version-switching question:

    I’m concerned that version-switching is just a secret password unless Microsoft is willing to enforce it.

    Say 5 years go by, and all the "bad" web developers get the message that if they want their site to work in the latest versions of all browsers, they should add <meta http-equiv="X-UA-Compatible" content="IE=edge"> in the header of their document.  In other words, the same forces that conspired to make doctype-switching worthless have now conspired to make version-switching worthless too.

    If that happened, would IE.next.next break the web, or start using something like <meta http-equiv="X-UA-Compatible-Era" content="IE=web2.0 NS=AOL">, which would be changed whenever the bad developers heard about it?

    – Andrew Sayers

  40. mike says:

    Chris,

    Break the web. It will thank you for it later.

    It’s not that other don’t get your perspective, we just shake our heads why why, oh god, why….

  41. Alan Gresley says:

    Hi Chris

    You must be on holidays. Question. Will IE8=edge still fall for *+html which targets IE7?

    Please Microsoft break the web.

  42. @mike – well then you don’t "get" my perspective, if you just shake your head.  Disagreement is rational, of course, but it is a real problem we’ve described.

    @Alan Gresley, actually no I’m not on holiday, just very busy preparing for MIX08.  I’m not sure I understand your question.

  43. Alan Gresley says:

    Hi Chris.

    What I mean is when IE8 is in standard mode, is IE8 going to use style rules that an author has given IE7

    *+html div {min-height:1%} /* hasLayout trigger */

    I know that some IE team member(s) has already tested some of my test cases on my site.

  44. David Naylor says:

    Chris, it would be interesting to hear your take on todays announcement.

  45. palmer says:

    This is good news. Any update on Microsofts attitude to ecmascript 4 aka Javascript 2. Will Ms endorse ecmascript 4?

  46. David Naylor says:

    Yes, I the ECMA-script thought struck me too…

  47. doug says:

    chris, I am having an issue with starting IE8 for WinXP up. I am getting an error for the "tfswshx.dll" component, and I don’t know why that’s happening, any help as to remedy this would be appreciated.

    Thanks in advanced.

  48. Steve says:

    Just tested a bunch of stuff in IE8.

    Must say…

    Bang Up Job Chris Wilson!  I wish the IE Blog had detailed the fixes earlier, but man I do appreciate each and every one!

  49. Daniel says:

    Chris,

    I really like to tell you how good IE8b1 feels so far. This is probably one of the greatest milestones I’ve ever seen for the web (and its standards).

    Congratulations and good luck finishing IE8!

  50. Andrew Sayers says:

    Yes, congratulations on a good week all round last week.  Needless to say, I withdraw my question.

    – Andrew

  51. Pestalence_XC says:

    IE 8 Fails Acid 2 test

    OK.. there are 2 ACID 2 tests available.. Microsoft’s IE 8 passes 1 of the 2 tests.. it fails the other.

    http://www.webstandards.org/action/acid2/guide/

    Note: Acid2 uses data URLs extensively (IE8 passes this test). To allow vendors that not yet support data URLs to test with Acid2, a version without data URLs has been published (IE8 Fails this test).

    First.. rendering Acid 2 test at the site Microsoft is using …

    http://www.webstandards.org/files/acid2/test.html

    IE 8 has no problem passing this test, however, there is a second Acid 2 test available which IE 8 does not pass, however it does not fail as badly as IE 7.

    http://hixie.ch/tests/evil/acid/002-no-data/

    Second, I found that trying to use search engines and sometimes forum boards, after doing a search.. you go to edit your search terms.. the cursor will not activate in the search box unless you click on an already typed word. If you have a blank search box, cursor will not activate.. this is annoying.

    Third, It is inconvenient to click IE 7 compatibility button only to have to close the browser and re-open it, then having to find the page you were on to see it rendered in an understandable way.. I have been to several pages that renders pages according to Acid 2 test 2 above.. sites such as the Adobe Flash site.. just updating Flash Player was a chore in IE 8 Native mode.. I had to switch back to IE 7 mode to get the updated Flash player.. links did not work correctly in IE 8 mode, text was over written with other text from different parts of page.. not a pleasant experience..

    Fourth, Microsoft Live Search functions do not render correctly either…

    go into Live Search, look up something.. click the Video button at the top.. you get video listings.. now click on the Duration link at the top right of the page.. the Duration list pops up on the left part of the page, not under where it should be as rendered in IE 7.

    So far no other problems to report, except that I can’t use the 64 bit browser for most pages (does not support 32 bit plug-ins) but that is fine with me.. so long as Microsoft keeps including both 32 bit and 64 bit browsers in a single download for 64 bit users, then all is cool.

    System Specifications :

    Intel Conroe 2.66 GHz @1333 MHZ FSB

    Patriot Extreme 4 Gb @ 800 MHz FSB Dual Channel (4 x 1024 Mb) DDR2

    Gigabyte N650SLI-DS4L motherboard

    BFG Geforce 8800 GTX OC 2 768 MB gDDR3 with 2 x 626 MHz clock cores

    I-INC TW191D 1440 x 900 5ms DVI monitor

    Hauppage HVR 1800 TV Tuner

    Western Digital Caviar 320 Gb 7200 RPM SATA HDD

    Samsung TSSTcorp TS-H625 DVD-/+RW, DVD-DL-R drive

    Mad Dog MD-16XDVD9 DVD-/+RW, DVD-DL-R External drive

    Ultra X3 1000 Watt PSU

    Micosoft Windows Vista Home Premium 64 bit

    Lexmark X2500 All-In-One printer

    all hardware is 100% functional… all software installed is 100% functional

  52. stjong says:

    Hope the team can make the IE8 done.

  53. handan says:

    I do is to web map programming, the map shows that this is the use of the mosaic map TABLE

    eg:

    <table>

    <tr>

    <td> <img src = "0_0.png" </ td>

    <td> <img src = "0_1.png" </ td>

    <td> <img src = "0_2.png" </ td>

    </ tr>

    </ table>

    But when I open this page often do not show the picture, I must be in the picture of regional mouse click can show that, Firefox can be directly displayed without onclick, I do not know what it is because I am distressed!

  54. sesli sohbet says:

    Chris,

    I really like to tell you how good IE8b1 feels so far. This is probably one of the greatest milestones I’ve ever seen for the web (and its standards).

    Congratulations and good luck finishing IE8!

  55. 생활지혜 says:

    딸국질은 횡경막의 경련에 의해서 일어 나는 것으로 쇼크를

    준다거나 잠시 호흡을 멈추면 낫는다.

    하지만 경우에 따라정신적 부담감으로 빨리 멎지 않을 때가 있다.

    멈추게 하는제일 좋은 방법은 심호흡을 한 뒤 견딜 수 있는데까지

    숨을 쉬지 않는 것이다.

    또는 숨을 멈춘채 찬물을 조금씩 마셔도효과가 있다.

    그래도 가라 앉지 않으면 조용히 숨을 내쉬면

    서 아랫배를 들이밀거나 때때로 배에 힘을 가득 준 뒤 호흡

    을 멈추는 복식호흡도 좋다.

    출처:http://cafe.daum.net/lifebean

  56. MSN Plus says:

    The thing is this just doesn’t really do it for me, prefer something a little less… mainstream.

  57. it help says:

    A really well explained article and has given me a nice idea for a project!

  58. sonbaharim says:

    sesli chat sohbet arkadaslık kızlar msn liseli kizlarsesli chat sohbet arkadaslık kızlar msn liseli kizlar

  59. arko says:

    I must be in the picture of regional mouse click can show that, Firefox can be directly displayed without onclick,

  60. Medyum says:

    Bang Up Job Chris Wilson!  I wish the IE Blog had detailed the fixes earlier, but man I do appreciate each and every one!

    thanks

  61. Medyum says:

    Another option is to give businesses a local policy/GPO option for the new IE that SA’s can set on their clients to determine how the IE engine of that workstations will react depending on the security zone of the site IE is working with.

    Sites in the Internet zone will use Doctype only, rendering the most standards based when the standards DocType is used.

    thank you

  62. aranansesli says:

    re: I feel happy, too… IE 8 fails Acid 2

    IE 8 Fails Acid 2 test

    OK.. there are 2 ACID 2 tests available.. Microsoft’s IE 8 passes 1 of the 2 tests.. it fails the other.

    http://www.webstandards.org/action/acid2/guide/

    Note: Acid2 uses data URLs extensively (IE8 passes this test). To allow vendors that not yet support data URLs to test with Acid2, a version without data URLs has been published (IE8 Fails this test).

    First.. rendering Acid 2 test at the site Microsoft is using …

    http://www.webstandards.org/files/acid2/test.html

    IE 8 has no problem passing this test, however, there is a second Acid 2 test available which IE 8 does not pass, however it does not fail as badly as IE 7.

    http://hixie.ch/tests/evil/acid/002-no-data/

    Second, I found that trying to use search engines and sometimes forum boards, after doing a search.. you go to edit your search terms.. the cursor will not activate in the search box unless you click on an already typed word. If you have a blank search box, cursor will not activate.. this is annoying.

    Third, It is inconvenient to click IE 7 compatibility button only to have to close the browser and re-open it, then having to find the page you were on to see it rendered in an understandable way.. I have been to several pages that renders pages according to Acid 2 test 2 above.. sites such as the Adobe Flash site.. just updating Flash Player was a chore in IE 8 Native mode.. I had to switch back to IE 7 mode to get the updated Flash player.. links did not work correctly in IE 8 mode, text was over written with other text from different parts of page.. not a pleasant experience..

    Fourth, Microsoft Live Search functions do not render correctly either…

    go into Live Search, look up something.. click the Video button at the top.. you get video listings.. now click on the Duration link at the top right of the page.. the Duration list pops up on the left part of the page, not under where it should be as rendered in IE 7.

    So far no other problems to report, except that I can’t use the 64 bit browser for most pages (does not support 32 bit plug-ins) but that is fine with me.. so long as Microsoft keeps including both 32 bit and 64 bit browsers in a single download for 64 bit users, then all is cool.

    System Specifications :

    Intel Conroe 2.66 GHz @1333 MHZ FSB

    Patriot Extreme 4 Gb @ 800 MHz FSB Dual Channel (4 x 1024 Mb) DDR2

    Gigabyte N650SLI-DS4L motherboard

    BFG Geforce 8800 GTX OC 2 768 MB gDDR3 with 2 x 626 MHz clock cores

    I-INC TW191D 1440 x 900 5ms DVI monitor

    Hauppage HVR 1800 TV Tuner

    Western Digital Caviar 320 Gb 7200 RPM SATA HDD

    Samsung TSSTcorp TS-H625 DVD-/+RW, DVD-DL-R drive

    Mad Dog MD-16XDVD9 DVD-/+RW, DVD-DL-R External drive

    Ultra X3 1000 Watt PSU

    Micosoft Windows Vista Home Premium 64 bit

    Lexmark X2500 All-In-One printer

    all hardware is 100% functional… all software installed is 100% functional

  63. aranansesli says:

    The thing is this just doesn’t really do it for me, prefer something a little less… mainstream.

  64. sesli chatli says:

    The thing is this just doesn’t really do it for me, prefer something a little less… mainstream…

  65. sohbetiguzel says:

    <td> <img src = "0_0.png" </ td>

    <td> <img src = "0_1.png" </ td>

    <td> <img src = "0_2.png" </ td>

    </ tr>

  66. SohbetciLer says:

    The thing is this just doesn’t really do it for me, prefer something a little less… mainstream.

  67. medyum says:

    First off, Happy Birthday!

    Now, why couldn’t you post the meta tag to the IE Blog?… that was like the ONLY thing in your post that I was looking for… (us up-to-date folks knew everything else)

    thanks,

    trevor

  68. 생활지혜 says:

    냉장고는 한번 설치하면 계속 사용하기 때문에 전력소모율이 매우 높다.

    한 가정의 한 달 전기요금 중 냉장고가 4분의 1을 차지한다는 통계도 있다.

    냉장고는 자주 여닫을수록, 보관하는 음식물이 많을수록 전력소모량이 많다.

    냉장고에는 음식물을 60%가량 채우는 것이 적당하다.

    방열기에먼지가 끼면 효율이 떨어지므로 자주 청소해야 전력소모를 줄일 수 있다

    0000

    출처:다음카페 생활의지혜!

  69. Sesli says:

    I… The thing is this just doesn’t really do it for me, prefer something a little less

  70. Büyü bozma says:

    The thing is this just doesn’t really do it for me, prefer something a little less… mainstream…

  71. hikaye says:

    This is fantastic. I am going to add it to my sites. Thanks!

  72. Sesli-SohbetChat says:

    Thank You very mach.. re: Not that you need me to tell you this… Bu başlığı ne diye istiyorsunuz?

  73. CRAZY says:

    dostlugun kardeslıgın bulustugu tek seslı goruntulu sıtesı http://www.sesliland.com.. ıyıseyırler

  74. Thank You very mach.. re: Not that you need me to tell you this… Bu başlığı ne diye istiyorsunuz?

  75. hakan bey says:

    Lol, Vista gibi değil pek çok kişi ve bu fark, Microsoft varsayalım. Ancak, yerine çok yakında Vista ile çok issuues olarak onlar için düzeltmek için çalıştı shouldn’ve yeni OC getirme.

    Kendim veya benim ekran dokunmaktan bile ekrana "sinema" da çok iş için ellerimi yetiştirme görmüyorum. Ben lazer fare kullanıyorum ve ancak bu ekranın bir ucundan diğerine geçmek için hareket.

    Emin, insanlar benim gibi gibi faydasız şeyler telefonlar "eyecandy", ancak yükseltir sadece i olduğu gibi-telefonlar, kısa bir süre sonra fark edeceksiniz bu kadar saçmalık.

  76. Seslicik says:

    Seslicik.Com Sesli Chat Sesli Sohbet

  77. Seslicik says:

    Seslicik.Com Kamerali Chat Kamerali Sohbet

  78. Sesli Chat Sesli Sohbet WebCam says:

    This is fantastic. I am going to add it to my sites. Thanks!

  79. This is fantastic. I am going to add it to my sites. Thanks!

  80. arifturkey says:

    This is a quarterly growth figure. It is standard practice in the United States to report growth data on an annual basis.

    thanks admin

  81. This is a quarterly growth figure. It is standard practice in the United States to report growth data on an annual basis.

  82. Thank you editors for the topic.Its include a lot of useful informations.i join this blog i couldnt see unnecessary arguments and it makes us happy thnx all moderator n editors.

    Thnx For http://www.videoklip.net and http://www.videoklip.eu http://www.ne-nerede.com http://www.seslichat.eu

  83. This is fantastic. I am going to add it to my sites. Thanks!

  84. Muharrem says:

    Tiklakop, http://www.tiklakop.com, seslichat, seslisohbet, chat, sohbet, kameralı sohbet, kameralı chat, sesli siteler, sesli site

  85. Muharrem says:

    Tiklakop, http://www.tiklakop.net, seslichat, seslisohbet, chat, sohbet, kameralı sohbet, kameralı chat, sesli siteler, sesli site

  86. Muharrem says:

    Tiklakop, http://www.tiklakop.org, seslichat, seslisohbet, chat, sohbet, kameralı sohbet, kameralı chat, sesli siteler, sesli site

  87. Muharrem says:

    Seslidizayn, Seslipanel, Panel Satısı, Sesli Chat Kurulumu, Sesli Site Kurulumu, Sesli Panel,

  88. Muharrem says:

    Seslibilisim, Seslipanel, Panel Satısı, Sesli Chat Kurulumu, Sesli Site Kurulumu, Sesli Panel,

  89. Muharrem says:

    Gncpanel, Seslipanel, Panel Satısı, Sesli Chat Kurulumu, Sesli Site Kurulumu, Sesli Panel,

  90. Muharrem says:

    seslistar, http://www.seslistar.com, seslichat, seslisohbet, chat, sohbet, kameralı sohbet, kameralı chat, sesli siteler, sesli site

  91. Muharrem says:

    seslisuper, http://www.seslisuper.com, seslichat, seslisohbet, chat, sohbet, kameralı sohbet, kameralı chat, sesli siteler, sesli site

  92. seslipanel says:

    Seslipanel,Sesli chat panelleri,Sesli sohbet panelleri

  93. cihan says:

    http://www.isvicresesli.com sesli sohbet sesli chat sitesi bekleriz…

  94. SESLİHİSAR <a href="http://www.seslihisar.com" title="seslihisar">Seslihisar</a> says:

    sesli chat odalarımıza hepinizii bekleriz

  95. <a href="http://www.seslisohbetevi.net">seslisohbetevi</a> says:

    Great!!! thanks for sharing this information to us!

  96. estetik says:

    I am happy to find this very useful for me, as it contains lot of information. I always prefer to read the quality content

    <a href="http://www.alimezdegi.com">Estetik</a&gt;

  97. SesliPanel says:

    The thing is this just doesn't really do it for me, prefer something a little less… mainstream

  98. radyo dinle says:

    radyo dinle online radyo dinle canlı radyo dinle http://www.bankoelitfm.net