Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T00:50:46Zhttps://gitlab.torproject.org/legacy/trac/-/issues/27590Display .onion alt-svc route in the circuit display2020-06-16T00:50:46ZTracDisplay .onion alt-svc route in the circuit displayNow that #24553 has re-enabled alt-svc, the Circuit Display should probably indicate when the connection was made via an .onion alt-svc. Currently it doesn't.
Feel free to use this for testing: https://perfectoid.space/test.php
When the...Now that #24553 has re-enabled alt-svc, the Circuit Display should probably indicate when the connection was made via an .onion alt-svc. Currently it doesn't.
Feel free to use this for testing: https://perfectoid.space/test.php
When the page turns green, click on the green https lock to see the circuit.
**Trac**:
**Username**: mahrudhttps://gitlab.torproject.org/legacy/trac/-/issues/27554Wrong Icon Shown on Windows 10 Start Menu (Tor Browser 8.5a1)2020-06-16T00:50:40ZTracWrong Icon Shown on Windows 10 Start Menu (Tor Browser 8.5a1)Firefox's Icon is Falsely shown instead.
Screenshot:
![http://prntscr.com/krutaf](http://prntscr.com/krutaf)
**Trac**:
**Username**: XashyarFirefox's Icon is Falsely shown instead.
Screenshot:
![http://prntscr.com/krutaf](http://prntscr.com/krutaf)
**Trac**:
**Username**: Xashyarhttps://gitlab.torproject.org/legacy/trac/-/issues/27511Add New identity button to toolbar2022-05-26T01:52:40ZTracAdd New identity button to toolbarPlease, make possible to put a "new identity button" in the toolbar.
**Trac**:
**Username**: isnaiterPlease, make possible to put a "new identity button" in the toolbar.
**Trac**:
**Username**: isnaiterhttps://gitlab.torproject.org/legacy/trac/-/issues/27506In RTL languages, the onboarding bubble covers the version info2020-06-16T00:50:19ZMark SmithIn RTL languages, the onboarding bubble covers the version infoWhen a right-to-left language is used, the onboarding bubble is (correctly) moved to the right side of the about:tor page. Unfortunately, the Tor Browser version information is not moved and so it is covered by the onboarding bubble. I w...When a right-to-left language is used, the onboarding bubble is (correctly) moved to the right side of the about:tor page. Unfortunately, the Tor Browser version information is not moved and so it is covered by the onboarding bubble. I will attach a screenshot.https://gitlab.torproject.org/legacy/trac/-/issues/27486Onboarding: "Visit an Onion" creates an "about:blank" loading page2020-06-16T00:50:11ZdmrOnboarding: "Visit an Onion" creates an "about:blank" loading pageSuch a loading page can make a user unsure what's going on.
In contrast, the "See My Path" button does not do this (i.e. it shows the URL).
(So it seems possible to fix this.)
(Encountered in TB 8.0)Such a loading page can make a user unsure what's going on.
In contrast, the "See My Path" button does not do this (i.e. it shows the URL).
(So it seems possible to fix this.)
(Encountered in TB 8.0)https://gitlab.torproject.org/legacy/trac/-/issues/27485Onboarding: user not taught *how* to open the security-slider dialog2020-06-16T00:50:10ZdmrOnboarding: user not taught *how* to open the security-slider dialog"Security" / "Choose your experience" / "Review Settings" Onboarding screen doesn't direct the user how open the security-slider dialog outside of the Onboarding screen.
A user may want to open this dialog again, and potentially knowing..."Security" / "Choose your experience" / "Review Settings" Onboarding screen doesn't direct the user how open the security-slider dialog outside of the Onboarding screen.
A user may want to open this dialog again, and potentially knowing how to return to Onboarding, they may take a very inefficient path through the Onboarding functionality instead of the simple means.
(Encountered in TB 8.0)https://gitlab.torproject.org/legacy/trac/-/issues/27484Onboarding: unintuitive not-navigation buttons, starting with "Circuit Displa...2020-06-16T00:50:10ZdmrOnboarding: unintuitive not-navigation buttons, starting with "Circuit Display" / "See My Path"The "See My Path" button's effects are unintuitive for a user at that point in sequence, and the button click may get skipped by people utilizing a different form of navigation through Onboarding.
Prior to "See My Path", each button was...The "See My Path" button's effects are unintuitive for a user at that point in sequence, and the button click may get skipped by people utilizing a different form of navigation through Onboarding.
Prior to "See My Path", each button was essentially a "go to next" button.
Nothing in the "Circuit Display" paragraph indicates it will have a different effect than that.
Furthermore, the button doesn't advance the Onboarding screen (unlike prior buttons) - it just marks "Circuit Display" as done, thus leaving either of these navigation paths:
* user directly clicking on "Security" (or later)
* closing the Onboarding window and re-opening it (which "advances" the Onboarding because "Circuit Display" was marked as done)
A user may thus //also// try to click the button again, being so far trained to expect the button to cause navigation.
A similar thing happens for "Security" / "Review Settings" and "Experience Tips" / "See FAQs". However, for "Security", the text in the paragraph does indicate that something else will happen in response to the button click.
(Encountered in TB 8.0)https://gitlab.torproject.org/legacy/trac/-/issues/27483Onboarding: dialog closure is effectively treated as "read", causing screen a...2020-06-16T00:50:08ZdmrOnboarding: dialog closure is effectively treated as "read", causing screen advancementFor the first few screens in Onboarding:
Clicking anything outside the box in Onboarding closes the box //AND appears to mark the current screen as "read"//, thus changing the Onboarding experience to pop up the next screen when someone ...For the first few screens in Onboarding:
Clicking anything outside the box in Onboarding closes the box //AND appears to mark the current screen as "read"//, thus changing the Onboarding experience to pop up the next screen when someone opens it again. //This could be bad if the user doesn't actually read the screen before that, and doesn't recognize the Onboarding flow and go back to that screen.//
This seems to stop at "Circuit Display", probably because the "(not really) Next" button there does something other than advance the Onboarding screen.
Or maybe, alternatively, the first few screens are just auto-marked as "read". If that's the case, consider changing that to happen on button click / navigation.
(Encountered in TB 8.0)https://gitlab.torproject.org/legacy/trac/-/issues/27478Torbutton in Tor Browser 8 difficult to see in dark theme2020-06-16T00:50:02ZTracTorbutton in Tor Browser 8 difficult to see in dark themeTor Browser 8 includes Firefox ESR 60's "dark theme". It looks quite nice and I elected to enable it. The Torbutton (used for security, and tor network settings) is difficult to see in contrast to other icons. In dark mode it'd be nice t...Tor Browser 8 includes Firefox ESR 60's "dark theme". It looks quite nice and I elected to enable it. The Torbutton (used for security, and tor network settings) is difficult to see in contrast to other icons. In dark mode it'd be nice to enable a light grey version of it. Thoughts?
**Trac**:
**Username**: nsuchyrichardrichardhttps://gitlab.torproject.org/legacy/trac/-/issues/27476Remove gap between Tor Launcher window and main browser window2020-06-16T00:50:01ZArthur EdelsteinRemove gap between Tor Launcher window and main browser windowRight now, the Tor Launcher runs, and takes seconds or minutes to complete. The Tor Launcher window, though it says "Tor Browser" on the first screen is not recognizably a web browser, which may be confusing or scary to first-time users....Right now, the Tor Launcher runs, and takes seconds or minutes to complete. The Tor Launcher window, though it says "Tor Browser" on the first screen is not recognizably a web browser, which may be confusing or scary to first-time users.
Then the Tor Launcher window disappears, and then, before a browser window appears, there is a gap of varying length where no window is visible at all. On slow computers, this gap can be as much as tens of seconds and during that time there is no easy way to tell that Tor Browser is still running.
Often users, mistakenly guessing that Tor Browser has crashed, will double-click the Tor Browser app icon a second time and get messages like "Tor Browser is already running, but is not responding" or "Tor unexpectedly exited".
How can we solve this problem? I can think of a few possible solutions:
1. Don't hide the Tor Launcher window until the main browser window is visible. (Build the browser window hidden during the launch process so that it can appear fast as soon as the launch process is done.)
2. Show the main browser window below the Tor Launcher window while it launching process is running. Keep the Tor Launcher window modal (always on top) until it is finished.
3. Embed the Tor Launcher UI in the main browser window. Allow the user to enter a URL in the URL bar even before Tor is fully launched.
I favor (3) as having the best UX. But it is also the most difficult to implement.https://gitlab.torproject.org/legacy/trac/-/issues/27456When I follow the on-boarding instructions in order, it directs me to duckduc...2020-06-16T00:49:57ZTracWhen I follow the on-boarding instructions in order, it directs me to duckduckgo's onion before I setup the security settingsWhen I follow the on-boarding instructions in order, it directs me to duckduckgo's onion before I setup the security settings. Users might skip the very important step of setting their security settings and just start browsing duckduckgo...When I follow the on-boarding instructions in order, it directs me to duckduckgo's onion before I setup the security settings. Users might skip the very important step of setting their security settings and just start browsing duckduckgo's onion. The steps `Circuit Display` and `Security` need to be swapped to `Security` then `Circuit Display` so that it pushes the users to choose their security setting first before browsing the web.
Tested on TorBrowser 8
Image showing the button I clicked in on boarding step 4 to get too duckduckgo's onion
![https://s22.postimg.cc/aj4eo3gf5/Screen_Shot_2018-09-04_at_9.48.02_PM.png](https://s22.postimg.cc/aj4eo3gf5/Screen_Shot_2018-09-04_at_9.48.02_PM.png)
**Trac**:
**Username**: Dbryrtfbcbhgfhttps://gitlab.torproject.org/legacy/trac/-/issues/27399Leading Orfox users to Tor Browser Android2020-06-16T00:49:45ZAntonelaantonela@torproject.orgLeading Orfox users to Tor Browser AndroidThe Alpha release is using the Tor Browser icon at the Play Store. We decided it so users can start to relate Tor Browser for Desktop and Tor Browser for Android as the same family.
The TBA Alpha .apk is still using the Orfox icon. It m...The Alpha release is using the Tor Browser icon at the Play Store. We decided it so users can start to relate Tor Browser for Desktop and Tor Browser for Android as the same family.
The TBA Alpha .apk is still using the Orfox icon. It might be a problem because users with Orfox installed will see 2 Orfox apps on their desktops.
This ticket will track the efforts to make that user flow more smoothly and clear.
Use Cases
1. New users (no Orfox installed)
2. Migrated users (with Orfox installed)https://gitlab.torproject.org/legacy/trac/-/issues/27385https://snowflake.torproject.org/embed is confusing2020-06-13T18:19:14Zcypherpunkshttps://snowflake.torproject.org/embed is confusing`embed.html` should be the go to for embedding snowflake badges in webpages but it currently has a couple of problems,
1. No description, nothing to suggest to the lambda visitor about what to do.
2. Clicking on the badge redirects to ...`embed.html` should be the go to for embedding snowflake badges in webpages but it currently has a couple of problems,
1. No description, nothing to suggest to the lambda visitor about what to do.
2. Clicking on the badge redirects to the options page hosted in torproject.org, but this means that users who have first-party isolation manually enabled (as can be done in Firefox) won't be able to enable it on the page where embed.html is embedded.
Ideally what should be done is:
1. Small description ("Do you want to help censored users access the Tor network?") with a snowflake logo.
2. If user clicks on yes, then in that same iframe there's some JS check to see if WebRTC is disabled, if it is inform the user that WebRTC is necessary and perhaps add a link on how to enable it back.
3. If WebRTC is enabled, then load up snowflake.js and modernizr.js. Description should contain if the connection to the broker is done and is waiting for a client request, and if it is then maybe the logo should change as well as the description. (Since everything is done on the same page then there won't be any problems with first party isolation -- except with 3rd party cookies disabled)
Ideally it should be easy to embed into webpages if what's above is done, and should be small enough.
(cc'ing antonela of the ux-team for her opinions :)Arlo BreaultArlo Breaulthttps://gitlab.torproject.org/legacy/trac/-/issues/27348Tor Browser 8 onboarding UI bugs2020-06-16T00:49:40ZMark SmithTor Browser 8 onboarding UI bugsI am splitting the onboarding issues mentioned in #27301 out into this ticket:
The title of the card needs margin:
.onboarding-tour-description > h1 {margin: 16px 0;}
https://share.riseup.net/#CjGBhXPC7qgxKwwyh4Zljw
We really want gre...I am splitting the onboarding issues mentioned in #27301 out into this ticket:
The title of the card needs margin:
.onboarding-tour-description > h1 {margin: 16px 0;}
https://share.riseup.net/#CjGBhXPC7qgxKwwyh4Zljw
We really want green ticks' background that matches with illos green. How can we do it? is it css? Does Anto need to provide assets? FYI the green is #00DDB3
The scrollbars - Can we reduce margins or make them % to the windows in order to make them disappear?Mark SmithMark Smithhttps://gitlab.torproject.org/legacy/trac/-/issues/27308report bootstrap phase when we actually start, not just unblock something2020-06-13T15:30:07ZTaylor Yureport bootstrap phase when we actually start, not just unblock somethingRight now many bootstrap events get reported when the preceding task has completed. This makes it somewhat harder to tell what has gone wrong if bootstrap progress stalls.
[edit: The following isn't necessarily the best way to fix this...Right now many bootstrap events get reported when the preceding task has completed. This makes it somewhat harder to tell what has gone wrong if bootstrap progress stalls.
[edit: The following isn't necessarily the best way to fix this. It might be better to figure out how to report starting something when actually starting it.]
We should add completion milestones to bootstrap reporting. This makes bootstrap reporting more future-proof. If in the future we add a time-consuming task with (no bootstrap reporting) between two existing bootstrap tasks, it will be a little more obvious what's going on.
For example, say we have task X followed by task Z, but then we add a lengthy task Y without adding bootstrap reporting to it. In the old scheme without completion milestones, if Y stalls, the user sees:
* starting X
* starting Z
* [hang]
The user thinks Z has already started when no such thing has happened because Y is still in progress. If we add completion milestones, the user will see:
* starting X
* finished X
* starting Z
* finishing Z
in a normal bootstrap. If something gets stuck in task Y, the user will see:
* starting X
* finished X
* [hang]
This will make it more clear that something got stuck in between tasks.
In a one-line display like Tor Launcher, the completion milestones will normally flash by quickly and not be very visible to users. Completion milestones might make the NOTICE logs a bit more verbose.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/27301TB8.0a10 about:tor UI Bugs2020-06-16T00:49:36ZAntonelaantonela@torproject.orgTB8.0a10 about:tor UI BugsI collected some interface related bugs and detailed them here. Please, break up this ticket as you need it.
-------
**about:tor**
-------
Can we have "Tor Browser" at the URL Bar on violet instead of orange? Tor Violet is #7D4698
Can...I collected some interface related bugs and detailed them here. Please, break up this ticket as you need it.
-------
**about:tor**
-------
Can we have "Tor Browser" at the URL Bar on violet instead of orange? Tor Violet is #7D4698
Can we remove firefox's icon there?
https://trac.torproject.org/projects/tor/ticket/18058
-------
https://share.riseup.net/#u89ubutjh7zrgaSz_ZZbFg
we need a dynamic margin for the #bottom div. I suggest changing aboutTor.css line 122
#bottom { margin-top: 170px;
#bottom { margin-top: 10%;
-------
`Check out Tor Browser Manual` link should open in a new tab
-------
SVGs / pixeled .png on retina displays - Are we going to support .svg in about:tor on stable? [Depends on what is easier. We think using the @2/@3 .pngs might be the easier route. GeKo]
https://trac.torproject.org/projects/tor/ticket/27002
-------
Can we repeat the onions on the x-axis?
https://share.riseup.net/#F0UdZF1QI9CtMbLxTgW35g
-------
**Onboarding**
-------
The title of the card needs margin:
.onboarding-tour-description > h1 {margin: 16px 0;}
-------
https://share.riseup.net/#CjGBhXPC7qgxKwwyh4Zljw
We really want green ticks' background that matches with illos green. How can we do it? is it css? Does Anto need to provide assets? FYI the green is #00DDB3
-------
The scrollbars - Can we reduce margins or make them % to the windows in order to make them disappear?https://gitlab.torproject.org/legacy/trac/-/issues/27239TB team feedback on jump-to-80% work2020-06-16T00:49:21ZIsabela FernandesTB team feedback on jump-to-80% workHello TB team,
we would like your feedback on this work, and let us know if there is anything we need to know regarding this on Tor Browser side.Hello TB team,
we would like your feedback on this work, and let us know if there is anything we need to know regarding this on Tor Browser side.Tor: 0.4.0.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/27214Update descriptions for onboarding2020-06-16T00:49:16ZGeorg KoppenUpdate descriptions for onboardingThat's the ticket we should look at for the final strings for the onboarding in case there are changes we need.
Looking over the english ones I only found two things we should change, both on the onion services onboarding pane:
1) s/Br...That's the ticket we should look at for the final strings for the onboarding in case there are changes we need.
Looking over the english ones I only found two things we should change, both on the onion services onboarding pane:
1) s/Browser/browser. Or we could use "Tor Browser" instead of "our Browser".
2) I am quite hesiatant to use "ultimate" because that's a thing I feel we hardly can reach in a security/privacy context and should not claim we'Ve reached. Could we please use something else? Maybe "enhanced"?https://gitlab.torproject.org/legacy/trac/-/issues/27213Update about:tbupdate to new (about:tor) layout2020-06-16T00:49:15ZGeorg KoppenUpdate about:tbupdate to new (about:tor) layout`about:tbupdate` still shows the "old" greenish background and layout while `about:tor` got updated in #26960. I guess we should update it, too.`about:tbupdate` still shows the "old" greenish background and layout while `about:tor` got updated in #26960. I guess we should update it, too.https://gitlab.torproject.org/legacy/trac/-/issues/27200about:tor favicon should be the tb icon2020-06-16T00:49:13ZTracabout:tor favicon should be the tb iconabout:tor favicon is non-existent in tb 8.0a10
**Trac**:
**Username**: ProTipGuyFWIWWeLoveARMAabout:tor favicon is non-existent in tb 8.0a10
**Trac**:
**Username**: ProTipGuyFWIWWeLoveARMA