graceful degradation
Javascript - graceful degradation
Tuesday, October 28th, 2008 | javascript | No Comments
In the context of javascript, ‘graceful degradation’ involves ensuring that your site will still function for users that do not have javascript enabled. After reading a plethora of pro web standards literature and books such as Jeremy Keith’s DOM scripting, the importance of graceful degradation is drilled into your mind. When I commenced my project this semester, ensuring graceful degradation was a high priority.
However as I have read more web development material and tested many of the world’s largest sites with javascript disabled in my browser, it has become apparent to me that not everyone in the web development community considers graceful degradation important.
Over time, my opinion on the matter has also relaxed somewhat. Sure in a ‘web utopia’, every web site would support all possible combinations of browser set ups that a user may have. In reality however, there are other factors that come into consideration. According to the W3Schools website (http://www.w3schools.com/browsers/browsers_stats.asp), less than 5% of browsers have javascript disabled. If you are spending a large amount of time and resources ensuring compatibility for this minority group, a simple cost-benefit analysis may be useful. You may deduce that the benefit of supporting this minority is simply not worth the added cost of doing so. Especially considering that javascript adoption on all browsers (including mobile devices) is increasing each year. Although we may be passionate (and stubborn) about web standards issues like graceful degradation, sometimes it is necessary to sit back and consider other factors before making such decisions. If you agree, disagree or have any other thoughts on matters like this, please feel free to comment.