implement configuration portion of new Tor Launcher UI
This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/
The integrated progress bar is covered by #23262 (moved).
Activity
Trac:
Description: This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/The integrated status bar will be covered by a separate ticket.
to
This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/
The integrated progress bar will be covered by a separate ticket.
-
Trac:
Description: This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/The integrated progress bar will be covered by a separate ticket.
to
This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/
The integrated progress bar is covered by #23262 (moved).
Cc: brade, linda to linda -
We now have an implementation that, at a high level, matches Linda's latest design for configuration. The code is here: https://gitweb.torproject.org/user/brade/tor-launcher.git/log/?h=newui
If you want to try it out, replace your Tor Launcher with this one: https://people.torproject.org/~brade/builds/tl-newui-2017/tor-launcher@torproject.org.xpi (on OSX, replace the .xpi file under
TorBrowser-Data/Browser/*.default/extensions/; on Windows and Linux, replace the .xpi file underBrowser/TorBrowser/Data/Browser/profile.default/extensions/)Some things are not implemented yet, e.g., the help buttons (?) do not do the right thing. Feedback is welcome!
Replying to mcs:
This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/ Hangs on password submission.
-
Replying to cypherpunks:
Replying to mcs:
This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/ Hangs on password submission.
What hangs? Tor Browser? And does "password submission" refer to marvelapp.com, or to the Tor Launcher proxy configuration? If this is a Tor Browser problem, please provide steps to reproduce.
Replying to mcs:
Replying to cypherpunks:
Replying to mcs:
This ticket tracks implementation of the configuration portion of the new Tor Launcher configuration UI, as found here: https://marvelapp.com/3f6102d/ Hangs on password submission.
What hangs? Tor Browser? And does "password submission" refer to marvelapp.com, or to the Tor Launcher proxy configuration? If this is a Tor Browser problem, please provide steps to reproduce. "password submission" refers to marvelapp.com through Tor Browser with High Security:
19:14:49.691 Project with id '3f6102d' requires a password. 1 prototype-bundle.c6c8b4bddefe245de0fd.js:113Tor Launcher without port selection and copying log to clipboard - is this intended? "provide a bridge I know" -> "use my bridges"
Mark:
My feedback: yay!
The prototype accurately reflect the behavior/layout that I envisioned for Tor launcher. I like the network settings screen, and am excited about the simplicity of Tor launcher flow for the user, how much clearer what options should be chosen and when, and that people can see all their settings right before they connect. Kudos on getting everything that I designed to fit neatly into the current window size, even with the settings combination that took up the most space (inputting my own bridge lines + using a proxy).
What I think we should do next:
- the prototype doesn't incorporate all the text changes/include the moat option like the final version of the Tor launcher. That being said, I know that this is not the final version, and these changes would be made eventually.
- We should work on sizing/styling--font sizes, images sizes, placement, etc. I didn't specify any of this in the prototype, and haven't thought about it. I think it's most of the way there, except the initial Tor | Browser image looks a bit big, and some of the text might look better if the containers they were in were tinkered with a bit.
Thanks for creating the prototype!
-
Replying to cypherpunks:
"password submission" refers to marvelapp.com through Tor Browser with High Security: {{{ 19:14:49.691 Project with id '3f6102d' requires a password. 1 prototype-bundle.c6c8b4bddefe245de0fd.js:113 }}}
I assume you allowed JS for that site? I am not sure what is going on. Does it work on other security levels?
Tor Launcher without port selection and copying log to clipboard - is this intended?
Port selection has not been included in the initial setup wizard for a long time. It will still be available via the Network Settings window inside the browser.
Copy Log to Clipboard is still needed and should probably be added to the design (currently that button is shown in the setup wizard only after an error occurs; it is always shown in the Network Settings window).
"provide a bridge I know" -> "use my bridges"
I am not sure about "my" but I do agree that the current phrase is a little awkward. In any case, I think that comments about the text copy are welcome; they will be evaluated by Linda and others.
marvelapp.com link finally worked so here are the only flaws that I could decipher,
-
"if you are in a country that censors Tor (such as China, Iran, Syria)" -> "if you're" / Are you sure that Iran still blocks Tor? You should ask dcf if that's the case, and if it isn't then he can give you better examples of such countries (Turkey for instance).
-
"(not China)" is a bit confusing, is there any better wording ("doesn't work in China"/"works in China" or just a single "if you're in [China flag]" near meek-amazon and meek-azure)?
-
FWIW #11071 (moved) is related to point 2 above
Replying to cypherpunks:
- "if you are in a country that censors Tor (such as China, Iran, Syria)" -> "if you're" / Are you sure that Iran still blocks Tor? You should ask dcf if that's the case, and if it isn't then he can give you better examples of such countries (Turkey for instance).
We've talked and decided these were the countries we were going to use as examples.
- "(not China)" is a bit confusing, is there any better wording ("doesn't work in China"/"works in China" or just a single "if you're in [China flag]" near meek-amazon and meek-azure)?
I agree. I don't know how to word this more properly. I want a wording that:
- doesn't make it seem like obfs4/obfs3 is inferior because it's blocked in China
- incentivizes people to use obfs4/obfs3 if possible over meek-amazon/meek-azure
- doesn't lie and say that meek PTs only work in China, or that you should use them only if you're in China, since they do technically work everywhere.
I had a couple ideas, "works in china/works everywhere" would probably make everyone choose meek PTs, because it makes the meek ones sound much better. I would like to have obfs4 marked with "recommended" and the meek ones marked with "choose if you're in China," but since obfs4 is the default, people may click onward without looking at the other options. So I'd like to put "recommended, blocked in china" as the description for obfs4, and something else in parentheses for the meek ones. I'd be open to suggestions.
My best attempt so far, which I don't like too much: https://share.riseup.net/#8Ma-Xheamd2uJuId44dhcQ
I'd be open to suggestions.
After discussion, we decided to keep the descriptors as they are currently deployed (no mention of any countries, and with obfs4 as the recommended PT). You can see the lastest version of the prototype here: https://trac.torproject.org/projects/tor/attachment/ticket/23261/tor-launcher-redesign-v9.pdf
I'm now happy to call this iteration of the design done.
