#26324 closed defect (fixed)
Should we switch to "Tor Browser.app" from "TorBrowser.app" for macOS Tor Browser based on ESR60?
| Reported by: | gk | Owned by: | tbb-team |
|---|---|---|---|
| Priority: | Very High | Milestone: | |
| Component: | Applications/Tor Browser | Version: | |
| Severity: | Normal | Keywords: | ff60-esr, TorBrowserTeam201806 |
| Cc: | mcs, brade | Actual Points: | |
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
We should think about whether we want to follow Mozilla's "suggestion" to switch from "TorBrowser.app" to "Tor Browser.app" and what that would entail from an update perspective etc.
The nightlies made this transition and I tried to fix all relevant "TorBrowser.app" occurrences in the build script at least (but I might have missed some there and elsewhere).
Child Tickets
Change History (3)
comment:1 follow-up: 2 Changed 16 months ago by
comment:2 Changed 16 months ago by
Replying to boklm:
I see that the
mac-sandboxcontains a few references toTorBrowser.app, inprojects/tor-browser/Bundle-Data/mac-sandbox/.
The Mac sandbox has been non-functional since the first ESR52-based release (due to the addition of content sandboxing on macOS). We should remove it until we can devote engineering time to application sandboxing.
Regarding the general question of "Tor Browser.app" vs. "TorBrowser.app", I think we should add the space. This should not affect updates, since the .app can already be renamed by users to anything they like. The only thing that worries me is that Mozilla encountered some issues (but possibly unrelated) after they added a space to "Firefox Nightly". See https://bugzilla.mozilla.org/show_bug.cgi?id=1427000
comment:3 Changed 15 months ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Okay, then let's use "Tor Browser.app" and see what breaks.
I see that the
mac-sandboxcontains a few references toTorBrowser.app, inprojects/tor-browser/Bundle-Data/mac-sandbox/.