Description
Library version
v0.8.1 and v1+
Describe the bug
I have encountered an issue with the ua-parser-js library where the browser detection results for the QQ user agent are inconsistent between version 0.8.1 and versions v1.0.0 and above. The expected behavior is that the library should return "QQ" for the QQ browser user agent, but it returns "QQBrowser" in the newer versions.
To Reproduce
Verification Code:
import { UAParser } from 'ua-parser-js';
console.log(new UAParser('User Agent: Mozilla/5.0 (Linux; Android 14; V2183A Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/121.0.6167.71 MQQBrowser/6.2 TBS/047205 Mobile Safari/537.36 V1_AND_SQ_9.0.65_6588_YYB_D QQ/9.0.65.17370 NetType/WIFI WebP/0.3.0 AppId/537225141 Pixel/1080 StatusBarHeight/96 SimpleUISwitch/0 QQTheme/1000 StudyMode/0 CurrentMode/0 CurrentFontScale/1.0 GlobalDensityScale/0.90000004 AllowLandscape/false InMagicWin/0').getBrowser());Results:
using [email protected]:
{
name: "QQ",
version: "9.0.65.17370",
major: "9"
}
using [email protected]
IData {
name: "QQBrowser",
version: "9.0.65.17370",
major: "9",
type: undefined,
getItem: [Function],
withClientHints: [Function],
withFeatureCheck: [Function],
is: [Function],
toString: [Function],
then: [Function],
}
Expected behavior
The expected output for the QQ user agent should consistently return "QQ" across all versions of the library, rather than "QQBrowser" in versions v1.0.0 and above.
Additional context
This inconsistency could lead to issues in applications that depend on accurate browser identification for feature detection or analytics. I would appreciate any guidance on resolving this issue or any plans for addressing it in future releases.
Thank you!