Why? That trailing slash can cause different site behaviour (in "badly behaved" sites).

Hi, the trailing slash (if any) would prevent for instance Firefox to open the site
I noticed that when entering as an hyperlink https://www.google.com/ versus https://www.google.com, this is the reason of cutting this trailing slash.
This is not a real issue anyway since any invalid url will be rejected by the browser :-)

Firefox opens (from your post above) both equally well. If it's a defect in the QTextBrowser widget's URL handling, that's a different matter. (And another reason to take care with using it for active links.)

Really, just simplify it. If I enter something as simple as http://example.com/?key=value, your slash stripper fails. I'd dump all that code and just find the index of either "http://" or "https://" through to space and pass that string.

So if I say "the http protocol is indicated by a 'http://' or 'https://' prefix on a url", this will find the first "http" (between "the" and "protocol").

(Parsing plain text to active links is fraught with danger, too, as you noted on the main post.)

That's correct.
A better way would be to find the index of strChatText.indexOf("http://", 0) or strChatText.indexOf("https://", 0) and include some more checks.
But in any case if the link appears to be invalid the browser will deal with it and depict it as non sense.

I don't think relying on the browser to clean up is a safe option.

Hi Peter
IMHO The browser will merely not open the wrong url and issue a 404 page.

Take a look at Qt's QUrl. A simple check like QUrl(text).isValid() would go a long way.

It would be useful, if we retain the licence popup as a separate dialog, for these properties to be set there, too.

strChatText.mid(indx_http,indx_space-indx_http-cutslash is repeated. It would be easier to read if it were put into a variable (strUrl, perhaps).

I'd also suggest, to improve readability and reduce the likelihood of dubious URLs being misread, to use a fixed width font at 110% size (or 1.1rem).

Here is a short code modif prior I leave for a few days trip
I'll try to get connected while I'm out.
Cheers

code at: https://we.tl/t-ZGz7CK0XqG

Nice. With the check for http/https, this should mean at least half-way sane values go in. If it comes back invalid, the check below then catches it. I'd still like the text more readable than "normal" so it catches the reader attention and is clearer.