-
|
Hello, I'm using your library for fingerprinting and noticed that when accessing the userAgent or browser-related information in Opera, the value includes multiple browser identifiers: When parsing this string in JavaScript, I end up detecting multiple matches: Mozilla → true Chrome → true Safari → true OPR → true This makes it difficult to determine the actual browser the user is using. Ideally, I’d like to retrieve a single, resolved browser name like "Opera" instead of relying on parsing the full user agent string manually. Questions:
Thank you for your time — I appreciate your work on this library, and look forward to any guidance you can provide on improving browser detection accuracy. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hi @sagar9990! As far as I can tell, FingerprintJS does not rely on the User Agent string for identification at all. Detecting the browser name from the user agent string is a separate problem, outside the scope of FingerprintJS. It is solved by the commercial Fingerprint platform, but also by other open-source libraries like UAParser.js
For historical reasons, browsers lie about what they are inside the User Agent string. There is a nice explanation in this CoRecursive episode or on MDN. |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate your answer, and thank you for the clarification. Just a quick suggestion - it might be better to add another object for the base browser (something to clearly identify the browser name). This could help us avoid relying on multiple libraries like UAParser |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback! Something for the team to consider. cc @primarch42 |
Beta Was this translation helpful? Give feedback.
Hi @sagar9990!
As far as I can tell, FingerprintJS does not rely on the User Agent string for identification at all. Detecting the browser name from the user agent string is a separate problem, outside the scope of FingerprintJS.
It is solved by the commercial Fingerprint platform, but also by other open-source libraries like UAParser.js
For historical reasons, browsers lie about what they are inside the User Agent string. There is a nice explanation in this CoRecursive episode or on MDN.