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.
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)
From a link in the bug report, it's a WebKit rendering bug that was fixed over half a year ago. Either Chrome's release schedule doesn't include updating WebKit frequently or the fix was incomplete.
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.
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)
For a quick summary/reference: http://javascript.about.com/od/hintsandtips/a/Html-5-And-Nos...