Closed Bug 1103241 Opened 5 years ago Closed 5 years ago
.trackingprotection .ui .enabled
We are getting biased feedback on tracking protection because the only users who enable it are the ones comfortable with about:config. This probably limits us to the "wizards" segment, which is around 1% (https://blog.mozilla.org/ux/2013/08/firefox-user-types-in-north-america/) If we want to get user feedback from a broader population segment, the checkbox for tracking protection needs to appear regardless whether privacy.trackingprotection.ui.enabled is true.
Assignee: nobody → mmc
Status: NEW → ASSIGNED
Comment on attachment 8535686 [details] [diff] [review] Remove privacy.trackingprotection.ui.enabled Review of attachment 8535686 [details] [diff] [review]: ----------------------------------------------------------------- Hi Gavin, We discussed this in Portland and came to a general consensus that we needed a way to get more user feedback to improve this feature, and making this feature more accessible was important in able to do that. Attendees included Javaun, Erin Lancaster, ttaubert, sworkman, dveditz, ekr, mt, sstamm, phlsa, and me. Please let me know if you want to discuss. Thanks, Monica
Hi Monica! Javaun has been working through ways this week to get more information into the funnel to answer the key questions we need to answer before we have the next conversation about getting this feature on the trains. I'll ask him to connect with you, but we're probably a step or two away from un-bundling this from Polaris.
I haven't had a chance to status everyone. We're lining up user research and telemetry experiments for early January. The research will help us understand how users understand tracking and interact with the feature, the experiments will activate Tracking Protection for many more users and allow us to test different user notification methods. Thanks, J
(In reply to Chad Weiner [:chadw] from comment #4) > Hi Monica! > > Javaun has been working through ways this week to get more information into > the funnel to answer the key questions we need to answer before we have the > next conversation about getting this feature on the trains. I'll ask him to > connect with you, but we're probably a step or two away from un-bundling > this from Polaris. Hi Chad, Thanks for the update. Please note that even with this patch, it still is not on the trains because it's #ifdef NIGHTLY'ed. I hope that makes this patch easier to accept. Thanks, Monica
Comment on attachment 8535686 [details] [diff] [review] Remove privacy.trackingprotection.ui.enabled My read of Chad/Javaun's comments are that we don't want this just yet.
need info javaun. blocked on the research per comment #5
The user research and telemetry experiments will help us answer the questions that are blocking turning TP on. The telemetry experiments will be turning TP on for a larger audience so that we can collect statistically significant data and corroborate/refute the things we hear in the qualitative user research. UR starts Monday. Generally, we want to start generally: 1. What is user’s mental model of tracking? Is there a problem we can solve (and for which users). The unanswered questions blocking turning the UI on as is (and getting this onto the trains) are what we really want to uncover in UR/telemetry 2. Does our current experience meet user's needs and expectations for tracking protection 3. Do they notice breakage, and if so, are they willing to accept the tradeoff -- or do they blame Firefox.
What the bug tracking the UR? can you mark it dependent on this bug?
see comment 10
Component: DOM: Security → Preferences
Product: Core → Firefox
I don't think there is any tracking bug for the UR. The recap was in the internal summary.
Someone has updated the SUMO article to reference privacy.trackingprotection.enabled which works in all channels, so this pref doesn't make sense anymore anyway. https://support.mozilla.org/en-US/kb/tracking-protection-firefox
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.