Closed Bug 810794 Opened 13 years ago Closed 13 years ago

Setting to no accept 3rd party cookies

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox19 verified, firefox20 verified)

VERIFIED FIXED
Firefox 19
Tracking Status
firefox19 --- verified
firefox20 --- verified

People

(Reporter: tetsuharu, Assigned: tetsuharu)

References

Details

Attachments

(1 file, 1 obsolete file)

Firefox for Android cannot set to no accept 3rd party cookies. (So current implementation can config "network.cookie.cookieBehavior" to 0 or 2.)
Attached patch patch v1 (obsolete) — Splinter Review
Attachment #680565 - Flags: review?(margaret.leibovic)
I think we should ask Ian for some UX feedback here. Right now this pref is in the middle of a big list of checkboxes, so it might be weird to have a tri-state pref in the middle. +<!ENTITY pref_cookies "Cookies"> +<!ENTITY pref_cookies_accept_all "Accept all"> +<!ENTITY pref_cookies_not_accept_foreign "Not accept 3rd"> +<!ENTITY pref_cookies_disabled "Disabled"> I also think we need a better string than "Not accept 3rd". Maybe "Don't accept 3rd party" or "Disable 3rd party". I also think we should use "Enabled" instead of "Accept all" for consistency with "Disabled".
Keywords: uiwanted
Comment on attachment 680565 [details] [diff] [review] patch v1 The approach is good here, I just want to get UX input before making it an r+/
Attachment #680565 - Flags: review?(margaret.leibovic) → feedback+
Margaret, thank you for reviewing rapidly. (In reply to Margaret Leibovic [:margaret] from comment #2) > I also think we need a better string than "Not accept 3rd". Maybe "Don't > accept 3rd party" or "Disable 3rd party". I also think we should use > "Enabled" instead of "Accept all" for consistency with "Disabled". I agree your point. How do you think "Disabled all" instead of "Disabled"? This has a contrast with "Disabled 3rd party". But I don't conclude it is natural or not because I'm not native English speaker.
We have two other settings that are similar: "Automatic updates" and "Plugins" Both use "Enabled" and "Disabled", although the positioning in the list is different.
(In reply to Mark Finkle (:mfinkle) from comment #5) > We have two other settings that are similar: "Automatic updates" and > "Plugins" > > Both use "Enabled" and "Disabled", although the positioning in the list is > different. (I don't know about details of their implemenetations,) At list of "Plugins", I think that the positioning in it means a stage of preference. e.g. "Enabled (always)"->"Tap to play (when user activate)"->"Disabled (always)". And also I use same approach in attachment 680565 [details] [diff] [review]. But I seem that it is strange which the list of "Automatic updates"... I think it should be better with changing to this order: "Enabled"->"Only over Wi-Fi"->"Disabled".
I'm fine to add this in. My suggested text would be: +<!ENTITY pref_cookies "Cookies"> +<!ENTITY pref_cookies_accept_all "Enabled"> +<!ENTITY pref_cookies_not_accept_foreign "Enabled, excluding 3rd party"> +<!ENTITY pref_cookies_disabled "Disabled"> I am not hugely concerned with it being adjacent to checkbox list items, but I might rearrange things a bit, to keep more similar items together: Cookies Clear private data Tell sites not to track me [] Remember passwords [] Use master password [] Show search suggestions [] Send performance data [] Show product announcements [] > But I seem that it is strange which the list of "Automatic updates"... I > think it should be better with changing to this order: "Enabled"->"Only over > Wi-Fi"->"Disabled". I agree, that is a more logical ordering of choices.
(In reply to Ian Barlow (:ibarlow) from comment #7) > I'm fine to add this in. My suggested text would be: > > +<!ENTITY pref_cookies "Cookies"> > +<!ENTITY pref_cookies_accept_all "Enabled"> > +<!ENTITY pref_cookies_not_accept_foreign "Enabled, excluding 3rd party"> > +<!ENTITY pref_cookies_disabled "Disabled"> Thank you. I take them in a new patch. > I am not hugely concerned with it being adjacent to checkbox list items, but > I might rearrange things a bit, to keep more similar items together: I filed Bug 811285 and CCing you. > > But I seem that it is strange which the list of "Automatic updates"... I > > think it should be better with changing to this order: "Enabled"->"Only over > > Wi-Fi"->"Disabled". > > I agree, that is a more logical ordering of choices. I filed Bug 811284.
Attached patch patch v2Splinter Review
Update local strings (I take Ian's comment #7)
Attachment #680565 - Attachment is obsolete: true
Attachment #681022 - Flags: review?(margaret.leibovic)
Comment on attachment 681022 [details] [diff] [review] patch v2 Great! Thanks for the patch! Also, thank you for filing those follow-up bugs, as well.
Attachment #681022 - Flags: review?(margaret.leibovic) → review+
Keywords: uiwanted
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 19
Blocks: 812781
Entity wasn't changed here despite a string change. See blocking bug.
(In reply to Aaron Train [:aaronmt] from comment #13) > Entity wasn't changed here despite a string change. See blocking bug. Doh, that was a dumb mistake on my part. Sorry.
The setting was added on the latest Nightly. Closing bug as verified fixed on: Firefox 20.0a1 (2012-11-20) Device: Galaxy S2 OS: Android 4.0.3
Status: RESOLVED → VERIFIED
TCs added in Moztrap with new option for following versions: 19, 19 tablets, 20 , 20 tablets https://moztrap.mozilla.org/manage/case/5874 - options for Cookies https://moztrap.mozilla.org/manage/case/5876- default value for Cookies
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: