I question that is bug. It's quite common that browsers like Brave provide a reduced or fake useragent string.
You can see many discussions around the useragent topic of the years in the Brave community.

Check via this website what the browsers return as useragent.
https://browserleaks.com/client-hints
That would help developers to understand if there is a bug in the browser detection question.

The browser detection routine might need to capture more infos to see if the user agent string is wrongly parsed.
For the Brave browser it might be a JavaScript routine.
https://github.com/brave/brave-browser/issues/8216

Well but the information given by the question is incomplete.

Example with Edge 112.0.1722.48 in MS Windows:
Browserleaks site shows:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48
Limesurvey displays only
Chrome (112.0)

Example with Brave 1.52.130, Chromium 114.0.5735.198 in Android:
Browserleaks site shows:
Mozilla/5.0 (Linux; Android 11) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Mobile Safari/537.36
Limesurvey displays only
Chrome (114.0)

@tibor.pacalat is this a bug or an enhancement request?

@gabrieljenik I would argue that this is an enhancement request.

This is not a bug on LS but a request for expanding the reach of the detection script for newer browsers.

The Browser Detect question theme uses Bowser lib to identify the browser.

@ritapas Please, can you enter here with the different browsers and check?
https://bowser-js.github.io/bowser-online/

If this page detects a browser which LS doesn't, then we can probably update something to match it.
If not, then it means we may need a nother lib for detecting the browser, which is more kind of a feature request.

Thanks!

Hello @gabrieljenik, here you are.

Example with EDGE Version 112.0.1722.48 in MS Windows:
Bowser lib shows: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48

Example with BRAVE 1.57.53, Chromium 116.0.5845.114
Bowser lib shows: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Mobile Safari/537.36

Latest Brave browser in android is seen as Chrome, as well as Edge 107 on Windows PCs

LIbrary doesn't detect brave.
Browserleaks neither.

I understand Brave has its caveats.
Not sure what to do here.

Here is the JS related.
https://github.com/LimeSurvey/LimeSurvey/blob/master/themes/question/browserdetect/survey/questions/answer/shortfreetext/assets/scripts/browserdetect.js
If you have any suggestion, please let me know.

I have no clue about Brave detection, sorry. However, Edge (and other browsers') detection could be more... wordly.

Edge (and other browsers') detection could be more... wordly.

Ok, let's just make an example?
How is it coming vs expected?

Yes, sure.
Example with EDGE Version 112.0.1722.48 in MS Windows:
Bowser lib shows: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48
Limesurvey displays only:
Chrome (112.0)

I would expect the long string like in the Bowser lib page. But I admit maybe there's a use case in which the shorter way is better...

@gabrieljenik
Not sure why this bugreport is seen as a feature request.
If you look at the note from the 17th July I get the impression that this is an faulty behavior by the code.
https://bugs.limesurvey.org/view.php?id=18775#c76110
ritapas wrote:

Example with Edge 112.0.1722.48 in MS Windows:
Browserleaks site shows:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.48
Limesurvey displays only
Chrome (112.0)

Is "Chrome (112.0) the intended result? I don't think so.
I would expect "Edg/112.0.1722.48".

Ohh I see.

Well, not sure what is the version to show! There is one of each kind in that line! haha