BriskBard, CEF4Delphi, WebView4Delphi, WebUI4Delphi and WebUI4CSharp

This is more of a curiosity than an issue that caused a problem, but it seemed odd, so here it is described as a sequence of steps.

1. BriskBard is set with the default engine of WebView2.

2. With several WebView2 tabs open from normal use, I choose to open a new tab with Chromium.

3. While on the Chromium tab, turn on Tor Network in the Status bar. (I don't know much about Tor, but it seemed to work okay for visiting onion sites etc. which is very cool!)

4. Close BriskBard. It is set to not keep running on the task bar and to start with no open tabs, and I wait for it to be totally closed.

5. Then when I restart BriskBard what seemed odd is that once opened, a message appeared about "Connected to the Tor network"

Is that surprising? How could that be when I have no open tabs and the WebView2 engine is the default?

Hi,

The Tor Network can be accessed thanks to the Tor Expert Bundle https://www.torproject.org/download/tor/

The Tor Expert Bundle acts as a proxy but only the current BriskBard process can use it because it's protected.

The web browser tabs only have to configure the proxy settings to use the Tor proxy in order to navigate through the Tor Network. Chromium tabs can change the proxy settings at runtime but WebView2 tabs can only change the proxy settings while the WebView2 framework is initialized when BriskBard's splash screen is visible.

The Tor thread runs in a background thread while BriskBard is running waiting for some web browser tab that uses it but BriskBard doesn't connect to the Tor Network unless the user selected the the "Tor Network" option.

Due to the different ways to change the proxy settings and the possibility of having a custom startup web page that requires the Tor network I decided to run the Tor thread if the user selected the "Tor Network" option in the previous session.

Select any other proxy option in the settings and you won't see that notification the next time you run BriskBard.

salvadordf wrote: Thu May 15, 2025 6:56 am The Tor thread runs in a background thread while BriskBard is running waiting for some web browser tab that uses it but BriskBard doesn't connect to the Tor Network unless the user selected the the "Tor Network" option.

Due to the different ways to change the proxy settings and the possibility of having a custom startup web page that requires the Tor network I decided to run the Tor thread if the user selected the "Tor Network" option in the previous session.

Select any other proxy option in the settings and you won't see that notification the next time you run BriskBard.

That all sounds logical, (mystery explained!) and I did what you said and it worked.