The <noscript> tag was notoriously buggy and iritating cross-browser, so I can see why they wouldn't want to implement it, like the <blink> tag.<p>If you use something like modernizr, which replaces the "no-js" class on your <html> tag with "js", you can just have a <div> or <p> simulate what <noscript> would have been. Have it "display: none" if the element is a child of "js". (trick courtesy Paul Irish)<p>For a quick summary/reference: <a href="http://javascript.about.com/od/hintsandtips/a/Html-5-And-Noscript.htm" rel="nofollow">http://javascript.about.com/od/hintsandtips/a/Html-5-And-Nos...</a>
Is this one of the drawbacks of Chrome's insanely quick release schedule? We've seen the benefits, it's not surprising that there are some drawbacks.<p>I fail to believe that such a fundamental bug would have been in a major Firefox release, although stranger things have happened.
I keep getting 500 error :(<p><pre><code> Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error message and the query that caused it.</code></pre>