Well, it *used* to work, when Petruchio used <script> tags. Now that they've been replaced with an onLoad event handler, the problem is back.
Can we just get rid of the 'disable JavaScript on homenodes' option until it works? The placebo effect (i.e. 'the power of suggestion') is psychological. It has no effect on computers. A function must actually be implemented before it can have an effect.
When the checkbox does not do what it says it does, it widens the security hole that JavaScript presents. It leads people to believe they're protected, when they are only sheltered from the most obvious way of carrying out the 'threat.'
Maybe it should say something like...
"Disable <script> tags and comment out their contents on home nodes. This may make you feel good, but will not actually protect you."
...at least until it can actually disable JavaScript.
Yes, I'm aware that it's difficult to filter JavaScript in all of its forms.
Update:Browsers that run the script on Pertruchio's homenode:
- MSIE 5.1.3 (MacOS X)
- Opera 5.03b393 (Mac OS X)
- MSIE 5.50.4807.2300 (Win 2000)
- Netscape 4.08 (Win 2000)
/me notes that the alert box is displayed (minus the cookie's value) even if you're not logged in, so you can test it safely.
s!!password!;y?sordid?binger?;y.paw.mrk.;
print chr 0x5b;print;print chr(0x5b+0x2);
|