No, there should not be any extravagant side effects using the <noscript> in the head.
However, the following disadvantages of <noscript> exist:
- It only works if the browser does not support JavaScript or is disabled. The contents of the
<noscript> will be invisible if Javascript is blocked by a firewall. - User agents with very poor Javascript support will still ignore the contents of
<noscript> . - While most browsers support
<noscript> in the head, this is technically incorrect X (HTML), so your pages may not be checked.
IMO, what you want to do is very good, and that is the appropriate use of a tag. However, an even better solution would be to use the discovery function in your Javascript to enable Javascript functions, rather than using <noscript> to disable them.
If you are depending on the capabilities of HTML5, I would recommend the Modernizr library for this purpose.
Peter Olson
source share