Live data from Hacker News

NoScript contents are not shown in Chrome

code.google.com

1–9 of 9 posts

Re: NoScript contents are not shown in Chrome

#2
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.

I fail to believe that such a fundamental bug would have been in a major Firefox release, although stranger things have happened.

Re: NoScript contents are not shown in Chrome

#4

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. I fail to believe that such a fundamental bug would have been in a major Firefox release, although stranger things have happened.

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.

Re: NoScript contents are not shown in Chrome

#6

I keep getting 500 error :( 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.

Every Google code page is throwing 500 or 502 errors at the moment.

Re: NoScript contents are not shown in Chrome

#8
post #6

I keep getting 500 error :( 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.

Every Google code page is throwing 500 or 502 errors at the moment.

I had this issue for weeks. I finally jokingly tried logging out and everything worked for me. Could try that...

Re: NoScript contents are not shown in Chrome

#9
The tag was notoriously buggy and iritating cross-browser, so I can see why they wouldn't want to implement it, like the tag.

If you use something like modernizr, which replaces the "no-js" class on your tag with "js", you can just have a or

simulate what 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...