Open Bug 764433 Opened 9 years ago Updated 3 years ago

Request: Block third-party cookies and delete cookies upon exit and or history

Categories

(Firefox for Android :: General, enhancement)

14 Branch
ARM
Android
enhancement
Not set
normal

Tracking

()

People

(Reporter: tmp.bugzilla.mozilla.org, Unassigned)

References

Details

Firefox mobile lacks too important privacy features: (1) ignore third party-cookies and (2) delete cookies when the browser is closed. Combining this two settings, users may prevent web trackers from linking browsing sessions togheter and storing any information for long time periods.

Unlike other mobile browsers, Mozilla seems to be very concerned with user privacy and, since this feature is also lacking in Android 2.3.x native browser (I do not checked ICS) and Opera Mini (not tested in Opera Mobile), it may be a great selling point for Firefox mobile.
You can disable cookies in the settings menu. But an option to remove cookies on close would be good add-on or an additional setting.
Disabling the cookies will not suffice as it would prevent site logins and other cookie usages from working during the session. I'm trying to mimic my typical desktop usage where the option works great and picks the best of two worlds.

I wrote the add-on a few hours ago: https://addons.mozilla.org/en-US/android/addon/delete-cookies-on-exit/  -- This one was easy, but I'm yet to write another one to block third-party cookies.
Summary: Block third-party cookies and delete cookies upon exit → Request: Block third-party cookies and delete cookies upon exit
(In reply to Alexandre Erwin Ittner from comment #2)
> I wrote the add-on a few hours ago:
> https://addons.mozilla.org/en-US/android/addon/delete-cookies-on-exit/  --

Awesome. \o/
Status: UNCONFIRMED → NEW
Ever confirmed: true
Duplicate of this bug: 966494
Summary: Request: Block third-party cookies and delete cookies upon exit → Request: Block third-party cookies and delete cookies upon exit and or history
Duplicate of this bug: 1392083
You need to log in before you can comment on or make changes to this bug.