Project

General

Profile

Bug #8061

Feature #10491: Redesign the network configuration and startup

Remove "Tor is not ready" popup when launching the Tor Browser

Added by tchou about 3 years ago. Updated 5 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/11/2014
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:
Browser

Description

When you start TorBrowser before Tor is ready, there is a "Tor is not ready" pop-up, that ask to confirm if we want to start IceWeasel.

I feel we could remove it, because :
- it can lead to misunderstanding, like thinking that it could be a probleme using TorBrowser without Tor ready
- there is a notification about Tor connection


Related issues

Related to Tails - Bug #12269: "Tor is not ready" should not pop up when opening local documentation Resolved 02/27/2017

History

#1 Updated by sajolida about 3 years ago

  • Parent task set to #7437

For me this should be considered as a subtask of #7437. I don't see a good reason to treat this urgently rather than start working on #7438.

#2 Updated by intrigeri about 3 years ago

  • Subject changed from Remove "Tor is not ready pop-up" when lunching IceWeasel to Remove "Tor is not ready pop-up" when launching IceWeasel

#3 Updated by intrigeri about 3 years ago

  • Subject changed from Remove "Tor is not ready pop-up" when launching IceWeasel to Remove "Tor is not ready" popup when launching the Tor Browser

#4 Updated by intrigeri about 3 years ago

  • Category set to 176

#5 Updated by intrigeri about 3 years ago

sajolida wrote:

For me this should be considered as a subtask of #7437. I don't see a good reason to treat this urgently rather than start working on #7438.

I tend to agree.

What makes me doubt is:

  • #7438 will be dealt with by totally different people than those who could address this problem, so it's not as if fixing this one will "steal" time from those who "should" instead focus on #7438;
  • sometimes, making incremental progress is good to fight our tendency to postpone easy things until the big, hard thing is done;
  • if we agree that this change is desirable, then I think it's a trivial thing to do.

#6 Updated by intrigeri almost 3 years ago

  • Assignee set to sajolida
  • QA Check set to Info Needed

I'd like to hear what sajolida now thinks. No emergency.

#7 Updated by sajolida almost 3 years ago

  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

First of all, I think that this is low priority. What is the sense of opening Tor Browser before Tor is ready? I can only think about browsing the LAN and we're about to move this to a dedicated browser. So we anyway have to find a way of explaining to the user that this browser is useless until Tor is started. Which is a process that happens in the background until we have #7437.

I'm also wondering about what kind of experience people who will be opening Tor Browser will receive until Tor is ready. At the moment the error message is "The proxy server is refusing connections", which I think is hard to relate to Tor if you don't know what's going on.

So, unless we are able to change this error message to something saying "Tor is not ready", I think that doing this right now would create more problems than it solves.

#8 Updated by intrigeri almost 3 years ago

First of all, I think that this is low priority.

Agreed.

What is the sense of opening Tor Browser before Tor is ready? I can only think about browsing the LAN and we're about to move this to a dedicated browser.

Reading the doc while being offline?

So we anyway have to find a way of explaining to the user that this browser is useless until Tor is started.

I think we're already doing that with the "Time sync in progress" notification, so the current browser popup seems to be a duplicate to me, so I don't think it would need to be replaced if we remove it.

I'm also wondering about what kind of experience people who will be opening Tor Browser will receive until Tor is ready. At the moment the error message is "The proxy server is refusing connections", which I think is hard to relate to Tor if you don't know what's going on.

... unless one has read the "Time sync in progress" (or whatever it's called) notification, and is then waiting for the "Tor is ready" message.

So, unless we are able to change this error message to something saying "Tor is not ready", I think that doing this right now would create more problems than it solves.

With the extra info I'm providing above, I beg to disagree.

#9 Updated by intrigeri almost 3 years ago

  • Assignee set to sajolida
  • QA Check set to Info Needed

#10 Updated by sajolida almost 3 years ago

Reading the doc while being offline?

I forgot about this one, thanks.

... unless one has read the "Time sync in progress" (or whatever it's
called) notification, and is then waiting for the "Tor is ready"
message.

The big difference here is that the desktop notification are "out of the
way" and disappear on their own quickly. While the current warning when
you open the browser is "on your way" even if you didn't pay attention
to the desktop notifications.

With the extra info I'm providing above, I beg to disagree.

I fail to see which problem is fixed by removing that warning (the two
bullet points in the description of this tickets are not "problems" to
me). But I'm convinced that the "proxy" error until Tor is ready will
confuse people who didn't pay attention to the desktop notification. But
I have no proof of that, so I'm ok to try and see.

If it was possible change the "proxy" error message to something related
to Tor, then I would find that actually as good as and more elegant than
the current solution.

#11 Updated by sajolida almost 3 years ago

  • Status changed from New to Confirmed
  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

#12 Updated by intrigeri almost 3 years ago

The big difference here is that the desktop notification are "out of the
way" and disappear on their own quickly. While the current warning when
you open the browser is "on your way" even if you didn't pay attention
to the desktop notifications.

ACK. Not sure it's an advantage, but you have guessed this :)

With the extra info I'm providing above, I beg to disagree.

I fail to see which problem is fixed by removing that warning (the two bullet points in the description of this tickets are not "problems" to me). But I'm convinced that the "proxy" error until Tor is ready will confuse people who didn't pay attention to the desktop notification.

OK, I'll leave it at that. On this one I'll trust your intuition more than mine :)

But I have no proof of that, so I'm ok to try and see.

If it was possible change the "proxy" error message to something related
to Tor, then I would find that actually as good as and more elegant than
the current solution.

Indeed. I'd love it if someone investigated that option a bit before we implement what this ticket suggests.

In some Tor Browser (31.2.0esr-4.x-1 branch) source tree, I see:

browser/locales/en-US/chrome/overrides/appstrings.properties:proxyConnectFailure=Firefox is configured to use a proxy server that is refusing connections.
browser/locales/en-US/chrome/overrides/netError.dtd:<!ENTITY proxyConnectFailure.title "The proxy server is refusing connections">

Possibly we can ship our own overrides file somewhere and change the strings. Then we need to have our own version translated, and integrate it within l10n system etc. It would be worth thinking if this strings change would be better done in Tor Browser; perhaps their usecase makes this error have a different meaning than in ours.

Once properly split into subtasks, this could be a nice set of "Easy" tickets.

#13 Updated by sajolida almost 3 years ago

  • Type of work changed from Discuss to Research

#14 Updated by BitingBird almost 3 years ago

  • Category deleted (176)
  • Affected tool set to Browser

#15 Updated by intrigeri almost 3 years ago

Note that if one starts Tor Browser once (e.g. by clicking on a link in a notification message), they get this popup, and if one clicks another link (e.g. the "Tails documentation" one) later, then one gets the same popup again.

#16 Updated by intrigeri 10 months ago

  • Related to Bug #12269: "Tor is not ready" should not pop up when opening local documentation added

#17 Updated by u 5 months ago

  • Description updated (diff)

#18 Updated by u 5 months ago

  • Parent task deleted (#7437)

#19 Updated by u 5 months ago

  • Parent task set to #10491

Also available in: Atom PDF