Internet Explorer 8 passes the Acid2 test. Huzzah!But waitaminnit… What’s this stuff about forward compatibility by adding some new X-UA-Compatible header to my pages or my server? Am I reading this right? Are you telling me that in order for IE8 to use its fully compliant rendering, we have to add something new to our pages? And that if we don’t, it will fall back to rendering pages just like IE7? Is that what this means?That’s just dumb.[source]
Have you read the breakthrough novel of the year? When you are done with that, try:
In Search of Sungudogo by Greg Laden, now in Kindle
or Paperback
*Please note:
Links to books and other items on this page and elsewhere on Greg Ladens' blog may send you to Amazon, where I am a registered affiliate. As an Amazon Associate I earn from qualifying purchases, which helps to fund this site.
or Paperback
*Please note:
Links to books and other items on this page and elsewhere on Greg Ladens' blog may send you to Amazon, where I am a registered affiliate. As an Amazon Associate I earn from qualifying purchases, which helps to fund this site.
You’re behind the times. Microsoft changed their minds. IE 8 will render in super-standards mode by default.
My days as a software engineer are numbered. Now, most of my code will have to look like this:
if (/* Internet Explorer 6 */) {...} else if (/* Internet Explorer 7 */) {...} else if (/* Internet Explorer 8 */) {...} else { /* standards compliant browser */...}Ick.Don’t worry, nothing has changed. Sun still rises in the morning, it still rains in Scotland, and IE8 fails the Acid3 test.http://news.softpedia.com/news/IE8-Beta-1-vs-Firefox-3-0-Beta-3-vs-Opera-9-5-Beta-vs-Safari-3-Beta-The-Future-80345.shtml