This adds up to extra JavaScript and server-side functionality, which, to me, sounds like making it overly complicated for JavaScript detection. Then you can reference that on the server-side for consecutive calls. What you can do is to add some small JavaScript in your web page, which redirects the page or sends a form or XMLHTTPRequest to the server, which in turn stores the value in a cookie or session variable. You can check USER_AGENT headers and hope for luck, but it’s not a guarantee nor offering a consistent way. In my pragmatic mind, this pretty much renders noscript useless, if you want to be a 100% sure. There are proxy servers out there cleaning out JavaScript files with what it thinks is inappropriate content, over-zealous antivirus programs, firewalls preventing certain functionality, and so on. Second, noscript only tells you if JavaScript is enabled or not in the web browser not if it actually works. Not applicable if you want the content visible to everyone, and then having the interaction presentation enhanced with JavaScript. To begin with, content within the noscript element will only be visible to user with JavaScript disabled. While that definitely works to some degree, there are some issues with it. Just use the noscript element, I guess you’re thinking. However, if the end user doesn’t have JavaScript enabled or if it fails for any reason, you would want that toggled content to be visible immediately. It’s a pretty common scenario where, for instance, part of a tree navigation or different blocks in the web page are hidden for JavaScript-enabled web browsers, thus letting the end user toggle them. Many people ask me how I choose to address an situation where all content in a web should be available without JavaScript, but certain parts hidden if JavaScript is enabled.
SHOWHIDE JAVASCRIPT HOW TO
How to hide and show initial content, depending on whether JavaScript support is available Published on Tuesday, May 13, 2008
0 kommentar(er)
