fwsudia wrote:NoScript essential and Chrome useless without it. Firefox also has a cookie whitelist, but it's hard to use (~10 step process). It should be like NoScript, a one-button process to whitelist domain of current page.
It *is* a one-step process. In Firefox Tools > Options > Privacy, check "Accept cookies from sites", then from the drop-down window "Keep until.." choose "Ask me every time".
When you visit a site not already in either list (yes or no), you'll get a prompt advising of the cookie trying to be sent. You may check "Allow", "Allow for session", or "Deny". There is also a box, "Use my choice for all cookies from this site". If you check that, the choice becomes permanent. "Allow" = permanent whitelist. "Allow for session" = permanent whitelist for the cookie, but for that browsing session only. It will be deleted when the browser is closed. "Deny" = permanent blacklist.
It's only five clicks and typing the address in manually, then clicking Allow, etc. to do it manually. But there is no need, as per the above, only if you wish to edit a previous setting.
I posted a request to firefox/bugzilla, but a prior request is almost 5 years old.
Because it isn't a bug. See above.
Please implement one-button process to grab current domain and add to FF cookie whitelist,
It's there (see above), and it's a Firefox issue anyway, not a NoScript issue. NoScript does not handle cookies.
FF and Google beholden to advertisers, who don't want to block ad tracking cookies (or anything, which is why Google can't implement NoScript in Chrome).
FWIW, I've already
said the same thing.
and look into same thing for Chrome, which may be harder, since cookie whitelist needs to be coded from scratch there.
That is Google's problem, not a NoScript or Firefox problem. Please advise them of your concerns.
Thanks for doing this great security product.
Thank you for your kind words!
