Of course, rapid changes in technology mean that something might not work in *newer* versions, but usually it's older versions that you have to worry about. So from a testing/development perspective having such a policy makes a lot of sense. It sets bounds on what you have to test and lets you know what cool new features you can exploit. For example, say you're responsible for maintaining a library website and you want to add some neat new functionality that isn't supported in, say, IE6; if your policy says you only support IE7 or later then it makes it easy to know that that's OK (and you have something to back up your decision if a user complains!). Or maybe you're in the testing phase and working on Safari; if your policy says you only support Safari 5 or later, you don't have to test in earlier versions.
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Ron Gilmour
Sent: Thursday, August 02, 2012 10:29 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Browser Support
This strikes me as a strange thing to have a policy about. Between the rapid development cycles of Chrome and Firefox and the ever-expanding diversity of mobile platforms and browsers, I don't see how such a policy could possibly be kept current and meaningful.
Ithaca College Library