noscript.surrogate.popunder.replacement and cookies

[james48K]

Two main items:

1.) When you disabled the javascript and data uris, I noticed that whenever a user types one, a dialog appears explaining that they were disabled and how to undo this. I just want to add a note here thanking Giorgio for that, as I hadn't noticed it in the list of changes and could easily imagine spending a long time in Google otherwise trying to work out why javascript:alert() had stopped working in the address bar.

2.) After I went to noscript.net to confirm that this was in the list of changes, I decided to quickly check that bookmarklets were still working as stated by using a bookmarklet containing the following code:

javascript:alert(document.cookie+%22\n\nreferrer:%20%22+document.referrer)

Now, I should add that I use Cookie Monster (https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/) for cookie management, and because I've never needed cookies enabled on noscript.net, it's not in the list of allowed sites for that. So I was quite surprised when the javascript alert output the following as cookie data:

popunder=yes; popundr=yes; setover18=1

given that the noscript.net cookie wasn't even present on my hard drive!

I discovered from http://forums.informaction.com/viewtopic.php?f=7&t=3571&start=15 that this was a result of noscript.surrogate.popunder.replacement (and not in fact a real cookie); but wondered if there were any plans to make its behaviour more consistent with the user's cookie preferences and exceptions? Not for any practical reason, just to avoid confusion on the part of the user on other sites with cookies blocked.

Thanks,

James McLaughlin.

[Giorgio Maone]

but wondered if there were any plans to make its behaviour more consistent with the user's cookie preferences and exceptions?

Actually not, because this is even more useful on sites where you're disabling cookies (since the absence of the cookie triggers the popunder).
Anyway, like any other surrogate, this can be disabled site by site or even page by page, by creating and populating a noscript.surrogate.popunder.exceptions preference.