Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

After Cookies etc. deleted, WashingtonPost.com does not ask for permission for cookies, but does in Opera.

  • 5 àwọn èsì
  • 0 ní àwọn ìṣòro yìí
  • 1 view
  • Èsì tí ó kẹ́hìn lọ́wọ́ TyDraniu

more options

Could you kindly advise? WashingtonPost.com does NOT ask to accept cookies even after I deleted all cookies, website data and cache (but in Opera it does ask for cookies), after Firefox automatically deleting cookies and website data after closing Firefox, and after cleaning cookies, website data and cache with Ccleaner — WHY? Which mechanism of Firefox is exploited by WashingtonPost.com? And what should I do? Thank you!

Could you kindly advise? WashingtonPost.com does NOT ask to accept cookies even after I deleted all cookies, website data and cache (but in Opera it does ask for cookies), after Firefox automatically deleting cookies and website data after closing Firefox, and after cleaning cookies, website data and cache with Ccleaner — WHY? Which mechanism of Firefox is exploited by WashingtonPost.com? And what should I do? Thank you!

All Replies (5)

more options

If you are regularly clearing cookies on close then it doesn't make much difference either way. Cookies only become a problem when they persist over time.

Extensions can block cookie banners and auto-decline cookies. Does it still happen in Troubleshoot Mode?

more options

Yes. I had to sign in again after a restart in troubleshoot mode. Then I deleted all cookies, website data and cache, and washingtonpost.com still did not ask to accept cookies. However, when I wanted to answer your question, I had to sign in again in my Mozilla account. Any further thoughts on possible hidden cookies WashingtonPost.com finds in Firefox that it doesn't in Opera?

more options

Try disabling Tracking Protection for the site and disabling your extensions.

Also try disabling DNT and GPC.

more options

There were no extensions enabled. Tracking Protection and GPC were already disabled.

Enhanced Tracking Protection ETP was enabled, now disabled. After disabling ETP via the shield icon at the left of the address bar, WashingtonPost.com asked to accept cookies.

Thank you so much, zeroknight. You gave great advice" I appreciate it very much.

Well, now I wonder whether it would be better to read the WashingtonPost with ETP enabled. Any thoughts?

more options