#24371 closed task (fixed)

QA of Tor Launcher new UI

Reported by: isabela Owned by: brade
Priority: Medium Milestone:
Component: Applications/Tor Launcher Version:
Severity: Normal Keywords: ux-team
Cc: isabela, mikeperry, mcs, isis, nickm, gk, brade, catalyst, iry, adrelanos Actual Points:
Parent ID: #21951 Points:
Reviewer: antonela, isabela Sponsor:

Description

Follow the steps bellow to test the new UI.

Download the alpha 7.5a8:

https://www.torproject.org/projects/torbrowser.html.en#downloads-alpha

To avoid conflicts you might want to remove your current Tor Browser installation before installing this alpha. 

What to look for:

  • Review copy
  • Review UI
  • Test all different type of bridges settings
  • If possible test proxy settings

Attached to this ticket are all the screens related to the work done that we are reviewing.To get to the configuration wizard, click on 'cancel' as soon as Tor Launcher starts.

Child Tickets

TicketStatusOwnerSummaryComponent
#24446closedbradeTor Browser Network configuration window gives an error when you try to select a Pluggable Transport.Applications/Tor Launcher

Attachments (2)

Tor-Launcher-new-UI.png (1.7 MB) - added by isabela 21 months ago.
Map of all Tor Launcher screens that we redesigned
Connect_to_Tor.png (34.6 KB) - added by isabela 21 months ago.
msg displayed when there is a bridge configured and you click on connect on Tor Launcher

Download all attachments as: .zip

Change History (9)

Changed 21 months ago by isabela

Attachment: Tor-Launcher-new-UI.png added

Map of all Tor Launcher screens that we redesigned

comment:1 Changed 21 months ago by isabela

Reviewer: antonelaantonela, isabela
Type: defecttask

comment:2 Changed 21 months ago by mcs

Also, if you want something close to a "first run" experience, do the following:

  1. Start Tor Browser and allow bootstrapping to complete.
  2. Open about:config.
  3. Filter on extensions.torlauncher.prompt_at_startup and toggle that pref so its value is "true."
  4. Filter on extensions.torlauncher.default_bridge_type and reset that pref so it has an empty value.

That should get you close. An alternative of course is to download a fresh copy of Tor Browser or, if on macOS, discard your TorBrowser-Data folder.

Changed 21 months ago by isabela

Attachment: Connect_to_Tor.png added

msg displayed when there is a bridge configured and you click on connect on Tor Launcher

comment:3 in reply to:  2 ; Changed 21 months ago by isabela

Hi mcs and Brade. I followed these steps (after playing with the settings for a bit using the built-in bridges (PTs). And got the following msg when I clicked on 'connect':
https://trac.torproject.org/projects/tor/attachment/ticket/24371/Connect_to_Tor.png

Replying to mcs:

Also, if you want something close to a "first run" experience, do the following:

  1. Start Tor Browser and allow bootstrapping to complete.
  2. Open about:config.
  3. Filter on extensions.torlauncher.prompt_at_startup and toggle that pref so its value is "true."
  4. Filter on extensions.torlauncher.default_bridge_type and reset that pref so it has an empty value.

When I did step 4 above it had 'snowflake' there, so I cleaned it up before restarting the browser and getting that msg.

I think this is a bad experience but I want to know if the experience is like this for real or if this is a bug before opening a ticket.

The reason I think is a bad experience is that if I have some configuration already to connect to Tor, the 'connect' button should just use that to connect. Or is the connect button only for direct connecting to Tor?

comment:4 Changed 21 months ago by catalyst

I think the "connect" button means "connect directly to Tor". When I get a successful bootstrap with obfs4, the next time I start Tor Browser, it skips the connect/configure prompt. If I time-warp my tor so bootstrap hangs, then click cancel, I get the experience Isabela describes.

I think the remaining bits of state that cause that behavior in Tor Launcher are the Bridge lines in the torrc file. Maybe Tor Launcher also looks for other configuration lines it writes to torrc.

comment:5 in reply to:  3 ; Changed 21 months ago by brade

Replying to isabela:

... I followed these steps (after playing with the settings for a bit using the built-in bridges (PTs). And got the following msg when I clicked on 'connect':
https://trac.torproject.org/projects/tor/attachment/ticket/24371/Connect_to_Tor.png

This prompt is expected when there are bridge settings but the user clicks "Connect" (which means direct connection without bridges). You can also see this prompt if you Configure and choose a bridge and then go back to the main screen and click "Connect." Do you have a suggestion for alternate wording of this message to make it clearer?

I think this is a bad experience but I want to know if the experience is like this for real or if this is a bug before opening a ticket.

Maybe I misunderstand the steps you did to get to this error message, but I don't think that this is a typical experience for our users (users who edit about:config to change TorLauncher's preferences are not common; it is not recommended). The steps that Mark provided are missing at least one thing that you need to do to get a true "first run" experience: find your torrc and make it an empty file.

comment:6 in reply to:  5 Changed 21 months ago by catalyst

Replying to brade:

Maybe I misunderstand the steps you did to get to this error message, but I don't think that this is a typical experience for our users (users who edit about:config to change TorLauncher's preferences are not common; it is not recommended).

I think the more likely situation for users to encounter (if they aren't editing about:config) is if they configure a bridge and bootstrap fails (or they cancel before it succeeds), then restart. Their torrc will have the bridge config, but due to lack of successful bootstrap, extensions.torlauncher.prompt_at_startup won't be set.

comment:7 Changed 16 months ago by isabela

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.