TB 42720: Show what's new in the about:dialog.
Merge Info
Issues
Resolves
- #42720 (closed)
- mullvad-browser#xxxxx
- tor-browser-build#xxxxx
Related
- tor-browser#xxxxx
- mullvad-browser#xxxxx
- tor-browser-build#xxxxx
Merging
Target Branches
- 
tor-browser-!fixupstotor-browser-specific commits, new features, security backports
- 
base-browserandmullvad-browser-!fixupstobase-browser-specific commits, new features to be shared withmullvad-browser, and security backports- 
⚠️ IMPORTANT: Please list thebase-browser-specific commits which need to be cherry-picked to thebase-browserandmullvad-browserbranches here
 
- 
Target Channels
- 
Alpha: esr128-14.5 
- 
Stable: esr128-14.0 
- 
Legacy: esr115-13.5 
Backporting
Timeline
- 
No Backport (preferred): patchset for the next major stable 
- 
Immediate: patchset needed as soon as possible (fixes CVEs, 0-days, etc) 
- 
Next Minor Stable Release: patchset that needs to be verified in nightly before backport 
- 
Eventually: patchset that needs to be verified in alpha before backport 
(Optional) Justification
- 
Security update: patchset contains a security fix (be sure to select the correct item in Timeline) 
- 
Censorship event: patchset enables censorship circumvention 
- 
Critical bug-fix: patchset fixes a bug in core-functionality 
- 
Consistency: patchset which would make development easier if it were in both the alpha and release branches; developer tools, build system changes, etc 
- 
Sponsor required: patchset required for sponsor 
- 
Localization: typos and other localization changes that should be also in the release branch 
- 
Other: please explain 
Upstream
- 
Patchset is a candidate for uplift to Firefox 
- 
Patchset is a backport from Firefox - Bugzilla link:
- Upstream commit:
 
Issue Tracking
- 
Link resolved issues with appropriate Release Prep issue for changelog generation 
Review
Request Reviewer
- 
Request review from an applications developer depending on modified system: - 
NOTE: if the MR modifies multiple areas, please /ccall the relevant reviewers (since Gitlab only allows 1 reviewer)
- accessibility : henry
- android : clairehurst, dan
- build system : boklm
- extensions : ma1
- firefox internals (XUL/JS/XPCOM) : jwilde, ma1
- fonts : pierov
- frontend (implementation) : henry
- frontend (review) : donuts, morgan
- localization : henry, pierov
- macOS : clairehurst, dan
- nightly builds : boklm
- rebases/release-prep : dan, ma1, pierov, morgan
- security : jwilde, ma1
- signing : boklm, morgan
- updater : pierov
- windows : jwilde, morgan
- misc/other : pierov, morgan
 
- 
NOTE: if the MR modifies multiple areas, please 
Change Description
Added the "What's new" button to the about:dialog.
This involved some customization for the link itself (our version line is too long, so we move it to the following one) and the logic to create the URL, as I don't think it's worth to add custom replacements for our blog posts...
Unless we move this pref from 000-tor-browser.js to the branding directory.
At that point I could add a replacement that removes the dots.
However, I've thought of this possibility only when writing this MR description.
Let me know what you prefer.
In a commit I also added a replacement for BASE_BROWSER_VERSION for a MB-equivalent of this MR (which will be simpler).
How Tested
Applied these changes to 14.5a4 (not 100% sure of the link, the post hasn't been published yet) and 14.0.7.