You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To me this looks "permanent" enough unless there is major change in the user's device. However some users still occasionally experience a different fingerprint. Are there any data points from the above that might change in case a user's browser updates?
The text was updated successfully, but these errors were encountered:
For those who care, I've found out during testing that the JS property screen.availHeight can potentially change during a browsing session by a few pixels even if the user doesn't do anything. I believe this is what's causing the issue in my post above.
This property is used by these clientJs methods: getAvailableResolution() and getScreenPrint().
I am using the ff. data points to generate a fingerprint:
getBrowser()
getOS()
getOSVersion()
getScreenPrint()
getTimeZone()
getLanguage()
getFonts()
getCanvasPrint()
getEngine()
navigator.hardwareConcurrency
navigator.deviceMemory
navigator.maxTouchPoints
To me this looks "permanent" enough unless there is major change in the user's device. However some users still occasionally experience a different fingerprint. Are there any data points from the above that might change in case a user's browser updates?
The text was updated successfully, but these errors were encountered: