Posted 19 July 2011 - 10:27 AM
Posted 19 July 2011 - 12:07 PM
Perhaps the most cogent webdev reason to support this development mindset/process is not those browsing with scripting unavailable (3-30% depending on audience) but to more easily account for x-browser inconsistencies and potential future scalability problems.
Worse case scenario might require failover to the noscript element.
The NOSCRIPT element allows authors to provide alternate content when a script is not executed. The content of a NOSCRIPT element should only be rendered by a script-aware user agent in the following cases:
* The user agent is configured not to evaluate scripts.
* The user agent doesn't support a scripting language invoked by a SCRIPT element earlier in the document.
User agents that do not support client-side scripts must render this element's contents.
This is where you can plead for visitors to use a supportive browser or to allow scripting for your site if they do. Not sure what the percentage uptake on such messages - I see them frequently as tend to browse with scripting disabled - I do know that I do so infrequently.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users