The screen on desktop isn't an error per se – it looks like Connection Assist has been triggered, but the user has gone back to the initial "Connect to Tor" stage using the breadcrumb navigation. This would be analogous to an Android user using the back arrow to return to the initial connection screen.
Whereas the screen on Android is for the no-internet error. You may be able to trigger this in Tor Browser Alpha by turning your wifi off, potentially?
@donuts just updated the connect assist screens for internet error and blockage of Tor. Could you pls take a look at the mockups and lmk if I missed any other screen?
Also, should I remove the "Restart Tor Browser" from the final error screen, considering tor-browser#43554?
Note: the screenshots will be removed once everything's ready.
The only thing I can think of is the extra location check that we perform before the final error. In the previous designs, this was called "location-check" and was different from "location-error". However I vaguely recall that @henry was considering eliminating this screen recently for desktop, and I'm not sure if it still exists on Android too?
In the previous designs, this was called "location-check" and was different from "location-error". However I vaguely recall that henry was considering eliminating this screen recently for desktop, and I'm not sure if it still exists on Android too?
It still exists. We're referring to it as ConfirmRegion. To see it you can set torbrowser.debug.censorship_level to 2 and then choose "Automatic" after the first normal bootstrap fails.