[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #31286 [Applications/Tor Browser]: Include bridge configuration into about:preferences
#31286: Include bridge configuration into about:preferences
-------------------------------------------------+-------------------------
Reporter: gk | Owner:
| pospeselr
Type: task | Status:
| needs_revision
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-9.0-must-alpha, ff68-esr, ux- | Actual Points:
team, TorBrowserTeam201910 |
Parent ID: #10760 | Points: 15
Reviewer: | Sponsor:
| Sponsor44-can
-------------------------------------------------+-------------------------
Comment (by pospeselr):
I've amended the review4 branch to change the last commit to a fixup!
commit:
tor-browser: tor-browser fixup:
https://gitweb.torproject.org/user/richard/tor-
browser.git/commit/?h=bug_31286_review4
gk: I opted to move the existing strings to the DTD as I gathered from
acat's changes to securityLevel.js that DTD was what we were using going
forward (since those strings had originally been in a properties file in
tor-button).
Once tor-launcher is gone and its functionality has been completely
integrated into Tor Browser (9.5?) then the tor-launcher (and maybe also
tor-button?) can live nicely together in one place and the 'TorStrings'
module can mostly go away. I think it would make sense to do the string
merge at that point.
Given that new tor bootstrapping UX is going to be coming down the pipe
soonish, do we need --without-tor-launcher support? What dev scenarios
does that enable? If so, I'll create a bug to track doing that.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31286#comment:42>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs