With the new world of rapid browser releases I am trying to figure out how to define & implement our browser compatibility process.

Previously we would always support the latest major version of a browser plus one or two older major versions depending on the browser. When I say support, I mean we would proactively test against these browsers for each of our releases. We had a wider range or browsers that we had "reactive" support for where we would fix a problem if we received a ticket for it.

However, with the new rapid release schedule and the sanctity of major version numbers being violated we need to come up with a new solution. One of the ideas I have was to manually look at the release notes for each browser and make a decision based on those if this was really a major version release or not. For instance, Firefox 5 wouldn't require official testing as the rendering engine was the same as 4 for everything that mattered. Looks like 6 and 7 will be the same way.

Maybe Firefox 9 will have some major bug fixes for some of the standard CSS3 features that we use and we will need to explicitly test 9 for compatibility.

Example Release Schedule Before Firefox 9 IE 8+ Chrome 10+ Firefox 3.6 Firefox 4+

Example Release Schedule After Firefox 9 IE 8+ Chrome 10+ Firefox 4-8 Firefox 9

This obviously has it's drawbacks and I am wondering how other people are handling it in this new world.

Thanks all!

EDIT: Are we finally at a point where we can truly trust that the modern browsers are going to handle standards the same way and we don't need to worry about it other than verifying standards compliance?

Browsers aren't going to cheat and try to fix broken code anymore, etc?

  • I like to support the current and previous version of each browser, if I find a few things in ie6 for example that make the site completely unusable then I will fix it for that browser. Commented Jul 11, 2011 at 20:14
  • Nick: So that would mean that right now we would no longer support Firefox 3.6, and in another 6 weeks we would no longer support Firefox 4 (as 6 would be released.) That is way too fast of a phase out for us to expect our customers to support.
    – moshjeier
    Commented Jul 11, 2011 at 20:18

1 Answer 1


The same we we were handling things since the days of Netscape 4 vs IE6 -- writing apps geared towards web standards with some hacks in place for certain older but common browsers.

  • 1
    We are seeing problems with "standards" not being handled correctly between firefox and chrome for instance (let alone IE9) so I don't think we are at the point yet where we say we support standards instead of browsers.
    – moshjeier
    Commented Jul 11, 2011 at 19:28
  • Also, the more I think about it, that doesn't actually solve the testing portion of it.
    – moshjeier
    Commented Jul 11, 2011 at 20:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.