InformAction Forums

1. When you post a link, we assume that's the one with the problem, if you change it in the meantime, defeats the attempt to support it when it can't be recreated. If you had taken the trouble to read the rest of the thread, you would've known that I had moved the link that triggers NoScript's bug ...

You aren't seeing errors because I've already changed that link to a URL that won't upset NoScript. If you use this page:

http://www.undeadlinks.com/index2.php

You'll see the error upon clicking on the "Valid HTML" button.

That's how the W3C advised to link to the validator until recently. But, while I was perusing their site to find a source to quote, I noticed that they are now endorsing a different link format in their docs: http://validator.w3.org/check/referer while retaining compatibility with the older scheme. ...

Frankly, I'd rather have NoScript not make my site look malicious. :? For now, I've just disabled the link to W3C, hoping that the bug will soon be fixed. If the developers need that link again to check for NoScript's behaviour, please use this ad-hoc page: http://www.undeadlinks.com/index2.php Than...

I don't see anything labeled "Valid HTML". Do you mean the button labeled "W3C HTML 4.01"? Yes, it was shorthand for that button. Assuming you do, I don't see a XSS report on Fx 3.5.3 or Fx 3.0.14. I'm using NoScript 1.9.8.89 on Windows XP SP3. Perhaps it's a Linux problem. Does...

Hello, I noticed that NoScript 1.9.8.86 reports a XSS attempt from http://www.undeadlinks.com whenever the user clicks on the "Valid HTML" badge that links to the W3C HTML validator. The site does not use JavaScript, nor does it include objects from external sites. The issue has been notic...