InformAction Forums

I was trying to see the javascript effect in the Demo section of this page:

http://polarblau.github.com/stickySecti ... ticky-list

...and it didn't work. I had allowed scripts on the site using the NoScript icon, and the icon didn't indicate that anything else was being blocked, so I believed the demo must be broken.

It turned out that NoScript was secretly blocking a script after all. The javascript console showed this message:

[NoScript] Blocking nosniff Javascript served from https://raw.github.com/polarblau/sticky ... headers.js with wrong type info text/plain, inline and included by http://polarblau.github.com/stickySectionHeaders/

WTF? I can't think of any reason why NoScript should block scripts without indicating that it is doing so. It just leads to frustration.

The same problem occurs when I tell NoScript to allow scripts globally, which would seem to be a problem as well.

Link was broken.
Suppose this is it, http://polarblau.github.com/stickySectionHeaders/?
I agree, I think.
Somehow we should be notified without needing to open Error Console.

Perhaps the NoScript icon could go black or something like that, a visual indicator. (And then a context-menu option to view Error Console.)

Not sure it's worth the effort: careless developers like that will soon be forced adapt, since IE9 doesn't give any visual clue either of this (correct) blocking:

IE9 wrote: SEC7112: Script at https://raw.github.com/polarblau/sticky ... headers.js blocked because of a MIME type mismatch

(from IE9's console, deep buried inside IE9's developer tools)

(It's a shame F12, developers tools, wasn't included long long ago in IE. Who knows, may have actually even looked at IE had it been there. Quite odd that they include it now. Looks like there's some interesting stuff there. Maybe one day I'll take a look.)