Skip to main content

IE8 readiness

I know people have done in depth reviews etc..., but here is a quick a low down of what you need to do as a web developer to support IE8.

I am going to assume that you have been a standards based web developer for the last couple of years and that you have not been doing too many hacks to support IE7.

1) Add the new metatag in the top of the to force IE8 to render in standards mode.

<meta http-equiv="X-UA-Compatible" content="IE=8;FF=3;OtherUA=4" />

Without this tag a little button appears next to the location bar which allows the user to view the site in IE7 compatibility mode. You probably don't want to do this because you want people to view your nice standards compliant website and also the render mode is slightly different from real IE7 in any case.

2) If you were using conditional comments to catch IE and add some extra CSS, you will probably need to update the condition from

<!--[if IE]>
<link rel="stylesheet" type="text/css" src="ie-hacks.css" />


<!--[if lte IE 7]>
<link rel="stylesheet" type="text/css" src="ie-hacks.css" />

3) You will probably want to put the above tags in a conditional which is controlled by a parameter so you can switch back and forth easily while testing

<% if params[:ie] != '7' %>

<meta http-equiv="X-UA-Compatible" content="IE=8;FF=3;OtherUA=4" />

<!--[if lte IE 7]>
<link rel="stylesheet" type="text/css" src="ie-hacks.css" />

<% end %>

And then access the IE7 mode in the following manner

4) There is currently a known bug with the scrollHeight and scrollTop properties (this broke the Yahoo Rich Text Editor I had embedded in my site It does not appear to be fixed yet in the release version.

I am sure there is plenty more, but this is what I have discovered so far.


Anonymous said…
Your stylesheet seems to cut long lines of <pre/> elements when there's not enough space. I use 1024x1280 screen and I don't see the endings of «meta» element example.

Also, blogger seems to have unfriendly kind of comment filter. I have to manually encode «<» sign... shame.
Anonymous said…
Alternatively, you can refuse to support IE8's standards mode.

Good web designers should see that this approach goes against the whole principle of standards on the web which ultimately make our job easier and the users' experience better.

Support it and we'll all have to live with it. Ignore it and Microsoft might eventually release a working browser.
skuunk said…
Hi liori,
Thanks for the tip. It looked fine in my browser, but I removed the pre tags.

Blogger's rich text editor is notoriously difficult for people typing in code samples I am afraid

Popular posts from this blog

Master of my domain

Hi All, I just got myself a new domain ( ). The reason is that is offering cheap domain via and I thought after having this nickname for nigh on 10 years it was time to buy the domain before someone else did (also I read somewhere that using in your domain is the equivalent of an or email address...shudder...). Of course I forgot that I would have to re-register my blog everywhere (which is taking ages) not to mention set up all my stats stuff again. *sigh*. It's a blogger's life... In any case, don't forget to bookmark the new address and to vote me up on Technorati !

Elixir - destructuring, function overloading and pattern matching

Why am I covering 3 Elixir topics at once? Well, perhaps it is to show you how the three are used together. Individually, any of these 3 are interesting, but combined, they provide you with a means of essentially getting rid of conditionals and spaghetti logic. Consider the following function. def greet_beatle(person) do case person.first_name do "John" -> "Hello John." "Paul" -> "Good day Paul." "George" -> "Georgie boy, how you doing?" "Ringo" -> "What a drummer!" _-> "You are not a Beatle, #{person.first_name}" end end Yeah, it basically works, but there is a big old case statement in there. If you wanted to do something more as well depending on the person, you could easily end up with some spaghetti logic. Let's see how we can simplify this a little. def greet_beatle(%{first_name: first_name}) do case first_name d

Speeding up RSpec

So today I have been looking into getting our enormous battery of tests to run faster. I have yet to find anything that works for Cucumber, but I did find an interesting way to speed up RSpec which is detailed here. Basically, it seems that by not collecting garbage too frequently, you can make your tests run much faster (at the expense of memory management of course). We observed a 30% reduction in the time it takes to run an RSpec test suite. I did try to implement this on Cucumber, however because we need to store much more in memory to set up and tear down our objects, it meant that I kept running out of memory when I wasn't using the default Garbage Collection and the tests took even longer (so, buyer beware). I suppose if you had a small set of features though you might see some benefit.