User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Bebelis/16.0.2 Build ID: 20121104132537 Steps to reproduce: (Tested in the newest stable release, ie. 36.0.4, Linux and Windows) 0. Run the browser. When you run it first time, read the message: "Welcome to Firefox Committed to you, your privacy and an open Web." [yeah, right...] 1. Open cookie manager: a. click on "Open menu" icon b. choose Preferences c. choose "Privacy" tab d. click on "remove individual cookies" e. in the "Search" field write "google.com" f. in the list of cookies choose cookie(s) from "google.com"; write down cookie content in external editor, it is sth like: ID=...:TM=...:LM=...:S=... g. click on "Remove Cookie" button; cookie(s) from "google.com" disappear(s) h. close cookie manager and Preferences window 2. Close the browser (optional step; doesn't change anything). 3. Open cookie manager and search again for cookies from "google.com" (refer to step 1 above). 4. You will notice that cookie from google.com still exists; it is the same cookie that you supposedly removed in step 1.g. Actual results: "Remove Cookie" button doesn't work in case of google.com cookie. Expected results: "Remove Cookie" button works in all cases.
Component: Untriaged → Preferences
OS: Linux → All
Hardware: x86_64 → All
Tested also in Nightly (same result; "Remove Cookie" button is named "Remove Selected"). From about:buildconfig: "Built from https://hg.mozilla.org/mozilla-central/rev/5330c6f461a4"
Additional info: persistent cookie is named "PREF".
It seems that this persistent cookie is not sent during normal browsing (ie. when visiting google.com domain). I guess it is related with so-called "safebrowsing". Unfortunately, it is still impossible to remove it even when so-called "safebrowsing" is disabled.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1008706
I was predicting exactly this problem 6 years ago, see https://bugzilla.mozilla.org/show_bug.cgi?id=368255#c32 footnote .
You need to log in before you can comment on or make changes to this bug.