I think it all comes down to personal preferences and no you never HAVE TO make stuff work for older, broken browsers. It is perfectly legitimate to ask users t

I think it all comes down to personal preferences and no you never HAVE TO make stuff work for older, broken browsers. It is perfectly legitimate to ask users to use a different browsers if they are on an old browser. The best way to decide wether to spend time debugging or just screw it would to be ask yourself a couple of questions. How much of the user base will be using old browsers? Think if your user base is mostly geeks / people at home or non-technichal / people using school or work computers (with locked-down policies for downloading software) Can you spend less time on older browsers and make it gracefully degrade without losing functionality? If your website looks less beatiful on an older browser but the functionality still works, you can put a warning stating that the website will look better if the user changes browser, but that no functionality is changed. Can you postpone this debugging to later? Maybe you should focus on launching your product first and once you're mostly satisfied with what you have, your spend time debugging old browsers. This way, you can release quickly for the majority of people that would use your service.