Lets not abandon Javascript altogether, though. What can be done to ensure graceful degradation in most circumstances?
• To understand the consequences of noscript and design applications to address this possibility in all cases. If Javascript is only used to enhance the user experience, it may be acceptable to do nothing. • Adopt a “defensive” coding strategy. Use object, method and property checking, rather than browser “sniffing”, to work around most eventualities (see below). • Test scripts in as many browsers as you can get hold of to ensure that, in principle, your error handling is robust and debugged in a known range of browser environments. You may not identify all possible problems, but at least you will have made an honourable effort. • Ensure that client side scripting is not the final fallback for your Web application and ensure that server side solutions are available to address whatever shortcomings may arise with your client side script.
Related Questions
- The Window and Document objects are core Javascript features and can be expected in all circumstances, but which methods are supported?
- Lets not abandon Javascript altogether, though. What can be done to ensure graceful degradation in most circumstances?
- Are there any circumstances in which a separation agreement is invalid altogether?
