#29768: Introduce new features to users in Tor Browser -------------------------------------------------+------------------------- Reporter: antonela | Owner: tbb- | team Type: defect | Status: | needs_information Priority: High | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: TorBrowserTeam201903, tbb-8.5-must- | Actual Points: alpha | Parent ID: #25658 | Points: Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by mcs): Replying to [comment:10 dunqan]: > Would the consequences of this approach be that existing users could no longer return to the base onboarding once an update's been released? Yes. The update "track" (aka tour type) is selected if the browser has been opened at least once with an older version of the tour set (this is handled via hidden prefs named `browser.onboarding.tourset-version` and `browser.onboarding.seen-tourset-version`). So far we have only used one one tour set version, which is 2. When we release Tor Browser 8.5 we would bump that to 3, which means users who upgrade to 8.5 will be placed on the update track. New users will remain on the "new" track until we release a Tor Browser that has a tour set version higher than 3. The logic that implements tour selection is here: https://gitweb.torproject.org/tor- browser.git/tree/browser/extensions/onboarding/OnboardingTourType.jsm#n22 > I don't think we've got any data on how often users return to this feature after initial onboarding – do we? No, not unless some data (or feeling) was captured during the UX testing sessions. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29768#comment:11> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs