Tor Browser issueshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues2022-10-03T16:51:15Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40118Bundle https-everywhere in tor-browser instead of tor-browser-build2022-10-03T16:51:15ZAlex CatarineuBundle https-everywhere in tor-browser instead of tor-browser-buildFollowup from #40091 and tor-browser-build#40073: we should try to bundle the builtin https-everywhere extension entirely in tor-browser and avoid the parts in tor-browser-build. I tried this with a `Makefile.in` that unzipped the xpi in...Followup from #40091 and tor-browser-build#40073: we should try to bundle the builtin https-everywhere extension entirely in tor-browser and avoid the parts in tor-browser-build. I tried this with a `Makefile.in` that unzipped the xpi into `dist/fennec/assets/extensions/https-everywhere`, but there was some unexpected behaviour, see https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/42#note_2708014. We should investigate and fix this.Tor Browser: 10.5https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40718Application Menu items should be sentence case2022-03-17T18:38:19ZdonutsApplication Menu items should be sentence caseAn eagle-eyed user on the forum has pointed out that `New Identity` and `New Tor Circuit for this Site` are both in title case, whereas the rest of the Application Menu is sentence case. And they're not wrong!
Let's update to `New ident...An eagle-eyed user on the forum has pointed out that `New Identity` and `New Tor Circuit for this Site` are both in title case, whereas the rest of the Application Menu is sentence case. And they're not wrong!
Let's update to `New identity` and `New Tor circuit for this site` whenever we're in the neighborhood next.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40705"visit our website" link on about:tbupdate pointing to different locations2021-12-20T11:12:12Zdonuts"visit our website" link on about:tbupdate pointing to different locationsSome users are reporting that the link to "visit our website" on `about:tbupdate` is pointing at https://blog.torproject.org/new-release-tor-browser-110, which 404s. The actual URL of the blog post is https://blog.torproject.org/new-rele...Some users are reporting that the link to "visit our website" on `about:tbupdate` is pointing at https://blog.torproject.org/new-release-tor-browser-110, which 404s. The actual URL of the blog post is https://blog.torproject.org/new-release-tor-browser-11-0 with an extra `-`.
However, my install of TB 11 is pointing at https://blog.torproject.org/category/tags/tor-browser instead, and I have no idea why.
Ideally, I'd like to use the latter link across the board since it's more robust and less prone to breakage. However, we'll need to change it again when the new blog is rolled out since the [Tor Browser category will cease to exist](https://gitlab.torproject.org/tpo/web/blog/-/issues/40008#note_2758516).Tor Browser: 11.0 Issues with previous releaserichardrichardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40646Revert #40475 and inherit upstream fix2021-12-20T11:07:48ZMatthew FinkelRevert #40475 and inherit upstream fixLanded as 754191343e929e2bf78f5597ee727231625d174bLanded as 754191343e929e2bf78f5597ee727231625d174bTor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40604Review closed mozilla92 bug2021-09-09T16:40:30ZMatthew FinkelReview closed mozilla92 bughttps://bugzilla.mozilla.org/buglist.cgi?product=Core&query_format=advanced&resolution=FIXED&target_milestone=92%20Branch&order=priority%2Cbug_severity&limit=0https://bugzilla.mozilla.org/buglist.cgi?product=Core&query_format=advanced&resolution=FIXED&target_milestone=92%20Branch&order=priority%2Cbug_severity&limit=0Tor Browser: 11.0 Issues with previous releaserichardrichardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40564[meta] Evaluate if Tor Browser is meeting the needs of our users2022-01-31T16:54:17ZMatthew Finkel[meta] Evaluate if Tor Browser is meeting the needs of our usersTor Browser has many goals as defined in the [Design document](https://2019.www.torproject.org/projects/torbrowser/design/), but we should take a step backward and look at the larger picture of whether these goals are actually important ...Tor Browser has many goals as defined in the [Design document](https://2019.www.torproject.org/projects/torbrowser/design/), but we should take a step backward and look at the larger picture of whether these goals are actually important for the [people](https://community.torproject.org/user-research/persona/) we are trying to protect.
We should be able to justify our general design requirements through the needs of our users, instead of defining the strictest-possible private browser design and then applying that to all of the use cases. Indeed, this should influence tor-browser-spec#25021.
cc @duncan @nahTor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40488Transition to ESR912022-05-16T17:28:08ZGabagaba@torproject.orgTransition to ESR91* [ ] Audit components for ESR91 Tor Browser
* tracking,
* fingerprintability,
* Tor safety features in relation to various known attacks.
* [ ] UX Fixes
* [x] Rebase Tor Browser esr91 patches on top of mozilla-central* [ ] Audit components for ESR91 Tor Browser
* tracking,
* fingerprintability,
* Tor safety features in relation to various known attacks.
* [ ] UX Fixes
* [x] Rebase Tor Browser esr91 patches on top of mozilla-centralTor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40483Deutsche Welle v2 redirect2022-01-28T16:26:03ZMatthew FinkelDeutsche Welle v2 redirectTemporarily redirect DW's v2 address to their v3 address.Temporarily redirect DW's v2 address to their v3 address.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40466Prepare switch to mozilla912022-04-04T17:41:33ZboklmPrepare switch to mozilla91- [x] tor-browser-build#40330 (Make the list of android components updates for switch to mozilla91-based Fenix)
- [x] tor-browser-build#40331 (Update components for switch to mozilla91-based Fenix)
- [x] tor-browser-build#40332 (Update c...- [x] tor-browser-build#40330 (Make the list of android components updates for switch to mozilla91-based Fenix)
- [x] tor-browser-build#40331 (Update components for switch to mozilla91-based Fenix)
- [x] tor-browser-build#40332 (Update components for switch to mozilla91 (all platforms))
- [x] tor-browser-build#40333 (Add a temporary ff91esr target in rbm.conf)
- [x] tor-browser-build#40334 (Remove temporary ff91esr target in rbm.conf)
- [x] #40744 (Review developer notes for Firefox 91)
- [ ] # (Review GeckoView Changelog for gv91)
- [x] #40588 (Review closed mozilla91 bug)
- [x] #40461 (Rebase 11.0 patches on 91.0)
- [x] #40563 (Rebase 11.0 patches on 91.0b5)
- [x] android-components#40059 (Rebase android-components patches to v91.0.1)
- [x] android-components#40064 (Rebase android-components patches to v91.0.7)
- [x] android-components#40065 (Rebase android-components patches to v91.0.8)
- [ ] android-components# (Review MozAC Changelog for Fenix91)
- [x] fenix#40184 (Rebase Fenix patches to Fenix 91)
- [ ] tor-browser-spec#40020 (FF91 network audit)
- [ ] tor-browser-bundle-testsuite# (Update tests when switching to Fenix 91)
- [ ] fenix# (Review changes for Fenix91)
- [x] tor-browser-build#40347 (Make the list of toolchain updates needed for firefox91 on linux/macos/windows)
- [x] tor-browser-build#40305 (Update linux toolchain for switch to mozilla91)
- [ ] tor-browser-build#40102 (Move from Debian Jessie to Debian Stretch for our Linux builds)
- [ ] tor-browser-build#40049 (Use own LLVM for wasi-sdk builds)
- [ ] tor-browser-build#40353 (Re-enable rlbox for linux firefox91 builds and switch from lucetc to wasm2c)
- [x] tor-browser-build#40306 (Update windows toolchain for switch to mozilla91)
- [x] tor-browser-build#40307 (Update macOS toolchain for switch to mozilla91)
- [x] #40253 (`extensions.allowPrivateBrowsingByDefault` will be removed)
- [x] tor-browser#40652 (Verify that esr91 builds are reproducible)Tor Browser: 11.0 Issues with previous release2021-08-10https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40438Add Blockchair as a search engine2021-11-16T03:02:45ZMatthew FinkelAdd Blockchair as a search engineTor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40401Prepare switch to mozilla902022-04-04T17:41:31ZMatthew FinkelPrepare switch to mozilla90- [x] #40482 (Rebase tor-browser patches to 90.0b12)
- [x] tor-browser-build#40311 (Make the list of components updates for switch to mozilla90-based Fenix)
- [x] tor-browser-build#40312 (Update components for switch to mozilla90-based F...- [x] #40482 (Rebase tor-browser patches to 90.0b12)
- [x] tor-browser-build#40311 (Make the list of components updates for switch to mozilla90-based Fenix)
- [x] tor-browser-build#40312 (Update components for switch to mozilla90-based Fenix)
- [x] #40517 (Review developer notes for Firefox 90)
- [x] #40516 (Review GeckoView Changelog for gv90)
- [ ] #40515 (Review closed mozilla90 bug)
- [x] android-components#40057 (Rebase android-components patches for Fenix 90 beta 6 builds)
- [x] android-components#40058 (Review MozAC Changelog for Fenix90)
- [x] fenix#40173 (Rebase Fenix patches to Fenix 90 beta 6)
- [x] tor-browser-spec#40019 (FF90 network audit)
- [ ] tor-browser-bundle-testsuite#40025 (Update tests when switching to Fenix 90)
- [x] fenix#40178 (Review changes for Fenix90)Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40342Set `gfx.bundled-fonts.activate = 1` to preserve current bundled fonts behaviour2021-11-02T20:21:13ZAlex CatarineuSet `gfx.bundled-fonts.activate = 1` to preserve current bundled fonts behaviourAfter https://bugzilla.mozilla.org/show_bug.cgi?id=1686274 we should set `gfx.bundled-fonts.activate = 1` to keep the current bundled fonts behaviour.After https://bugzilla.mozilla.org/show_bug.cgi?id=1686274 we should set `gfx.bundled-fonts.activate = 1` to keep the current bundled fonts behaviour.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40275Prepare switch to mozilla85 for mobile2021-10-12T21:36:30ZMatthew FinkelPrepare switch to mozilla85 for mobile- [x] tor-browser-bundle-testsuite#40014
- [x] android-components#40033
- [x] android-components#40034
- [x] android-components#40036
- [x] fenix#40130
- [x] fenix#40131
- [x] fenix#40132
- [x] fenix#40134
- [x] tor-browser-build#40190
-...- [x] tor-browser-bundle-testsuite#40014
- [x] android-components#40033
- [x] android-components#40034
- [x] android-components#40036
- [x] fenix#40130
- [x] fenix#40131
- [x] fenix#40132
- [x] fenix#40134
- [x] tor-browser-build#40190
- [x] tor-browser-build#40191
- [x] #40276
- [x] #40277
- [x] #40278
- [x] #40279
- [x] #40280
- [x] #40293
- [x] tor-browser-spec#40012
- [x] torbutton#40027Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40253`extensions.allowPrivateBrowsingByDefault` will be removed2021-12-15T18:18:46Zemyb`extensions.allowPrivateBrowsingByDefault` will be removedThe Mozilla team is going to remove `extensions.allowPrivateBrowsingByDefault`. This setting is `true` in Tor Browser and `false` in vanilla Firefox.
Will this cause problems? 💣
See [Mozilla's issue](https://bugzilla.mozilla.org/show_b...The Mozilla team is going to remove `extensions.allowPrivateBrowsingByDefault`. This setting is `true` in Tor Browser and `false` in vanilla Firefox.
Will this cause problems? 💣
See [Mozilla's issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1661517).Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40221Adapt nightly update URL2022-07-09T03:56:21ZGeorg KoppenAdapt nightly update URLWe patch the nightly update URL in `tor-browser-build` ad-hoc but we should move that out of `tor-browser-build` into a proper `tor-browser` patch.We patch the nightly update URL in `tor-browser-build` ad-hoc but we should move that out of `tor-browser-build` into a proper `tor-browser` patch.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40220Make sure tracker cookie purging is disabled2022-11-23T16:28:54ZAlex CatarineuMake sure tracker cookie purging is disabledThis was enabled in 84, and uplifted to 83 (https://bugzilla.mozilla.org/show_bug.cgi?id=1675596). We should probably disable that pref, even though in `GeckoView` we may be setting it to `false` already via `ContentBlocking.java`.This was enabled in 84, and uplifted to 83 (https://bugzilla.mozilla.org/show_bug.cgi?id=1675596). We should probably disable that pref, even though in `GeckoView` we may be setting it to `false` already via `ContentBlocking.java`.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40191Language not spoofed for en-CA and en-UK2021-08-04T19:46:37ZAlex CatarineuLanguage not spoofed for en-CA and en-UKIf a user installs an en-US tor-browser and then changes it to `English (Canada)` or `English (United Kingdom)` then neither the "locale spoofing prompt" is shown nor `Accept-Language` is spoofed (e.g. for Canada it's `en-CA,en-US;q=0.7,...If a user installs an en-US tor-browser and then changes it to `English (Canada)` or `English (United Kingdom)` then neither the "locale spoofing prompt" is shown nor `Accept-Language` is spoofed (e.g. for Canada it's `en-CA,en-US;q=0.7,en;q=0.3`). The prompt is not shown because of https://searchfox.org/mozilla-central/source/toolkit/components/resistfingerprinting/RFPHelper.jsm#196. Besides, given `javascript.use_us_english_locale=true` will not be set, I guess the non-spoofed locale will also be accessible via some JS APIs.
I'm not sure about the right solution, though. Should we show the spoofing prompt for these cases too? Or should we always spoof these two cases by default?Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40184Consider setting pref widget.disable-native-theme-for-content = true2023-05-22T12:02:39ZAlex CatarineuConsider setting pref widget.disable-native-theme-for-content = trueI have not done a lot of testing, but this may help solving issues like #22137.I have not done a lot of testing, but this may help solving issues like #22137.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40170Decide how we should notify users that their OS won't be supported in the nea...2021-12-07T10:14:55ZMatthew FinkelDecide how we should notify users that their OS won't be supported in the near futureImmediately, we have:
- [x] #40049
- [x] #40136
We'll have more in the future, so we could create a more general plan now.Immediately, we have:
- [x] #40049
- [x] #40136
We'll have more in the future, so we could create a more general plan now.Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40159Drop plugin support2021-11-02T20:44:09ZPassword is "Cypherpunks Write Code" without quotescypherpunks@mailinator.comDrop plugin supportNot a duplicate of #19508, just drop plugin support.
Flash will die in the end of 2020 but it because it reveals user IP, it should never be used on Tor Browser.
Other plugins are already dead.Not a duplicate of #19508, just drop plugin support.
Flash will die in the end of 2020 but it because it reveals user IP, it should never be used on Tor Browser.
Other plugins are already dead.Tor Browser: 11.0 Issues with previous release