Expose Tor log in `brave://tor`

Description

A friend of mine told me that he’s found our Tor support quite unreliable on his Linux desktop (it’s possible he’s running into #8076 or #8129 at the moment).

What he suggested is that we expose the tor daemon log somewhere so that tech-savvy users can more easily figure out what’s wrong (and send us useful bug reports).

Orbot on Android does this in a nice way, but perhaps all we need for an MVP would be to redirect the daemon log file to an in-memory structure and make it viewable from an internal URL like brave://tor.

Designs

The Tor connection status is displayed prominently on the NTP with a flashing indicator to draw attention and show progress. This would give some hint that the reason why NTP is not connecting to a webpage that a user entered is because it’s waiting for this Tor connection to complete. For users who are so inclined to dig into the details, View logs links to brave://tor.

The new, simplified NTP design ensures that no scrolling would occur for all but the very smallest screens - the content height is not much longer than an extension panel.

User flow

Search bar

The search bar has DDG set as the default. The user can click on the search bar dropdown to select a different SE for a particular search query.

Keyboarding

Assets

Figma: https://www.figma.com/file/5THkuEtO2Ewn9LfqrHZP9a/Desktop-Private-and-TOR-Windows?node-id=102%3A2574

[karenkliu]

Designs added!

[fmarier]

Now available at brave://tor-internals/.