Opened 5 months ago

Closed 5 months ago

#34321 closed defect (fixed)

Add What's New Onboarding Item

Reported by: sysrqb Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: ux-team, tbb-9.5, TorBrowserTeam202005R,
Cc: antonela, acat, gk, mcs, brade Actual Points:
Parent ID: #31660 Points:
Reviewer: Sponsor:


We should have something included in the 9.5 release onboarding for the new features. Antonela and I decided we can have one new entry named "What's New" (following Mozilla's new onboarding experience). This entry simply has a link to a webpage where new features are described.

The webpage is currently being developed at ​

Child Tickets

Change History (4)

comment:1 Changed 5 months ago by sysrqb

Cc: gk mcs brade added
Status: newneeds_review

I have a branch for review at:


I'm not very happy about my choice of strings.

Based on brade and mcs' suggestions in comments 24, 25, and 26, the Onboarding experience behavior is now different between new installations and upgrades. After upgrading, a user should see the Onboarding bubble ("See what's new in Tor Browser") and when that is clicked the "Release Notes" webpage should open in a separate tab. At the same time, the Onboarding tour is marked as completed and the bubble is hidden on about:tor. The onboarding overlay is never shown to the user.

With a new installation, the user sees the current onboarding overlay with the addition of a "Learn More" tab. The major changes in this situation are when the user clicks the "Done" button on the Onion Services tour and when the user directly clicks on the "Learn More" tab. In both of these cases the "Release Notes" page is opened in a separate tab, the "Learn More" item is marked as completed, and the overlay is hidden.

Continuing to use "Done" as the string on Onion Services button is possibly confusing, but the behavior is nearly the same as before.

Last edited 5 months ago by sysrqb (previous) (diff)

comment:2 Changed 5 months ago by sysrqb

For testing the update scenario:
1) Open about:config
2) Change browser.onboarding.state to default (if not currently)
3) Change browser.onboarding.tour-type to update (it should be new)

about:tor should automatically notice these changes and provide the new behavior.

comment:3 Changed 5 months ago by acat

Works for me.

comment:4 Changed 5 months ago by sysrqb

Resolution: fixed
Status: needs_reviewclosed

After discussing this on #tor-dev, gk and mcs reviewed the patch.

I rebased the patch onto tor-browser-68.9.0esr and merged it as commit db3ccb2a11256421f5d8db7caad10a5a2c98def5 on tor-browser-68.9.0esr-9.5-1. I cherry-picked it as commit d9016507dc5dd4910023b29df339aff63fd5d9a1 onto tor-browser-68.9.0esr-10.0-1.

Thanks everyone!

Note: See TracTickets for help on using tickets.