We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
Cromite a popular fork of chromium with many privacy features, has a feature called "viewport size protection". The feature is added through this patch: https://github.com/uazo/cromite/blob/master/build/patches/Viewport-Protection-flag.patch
When this feature is enabled, brotector detects some odd behavior from cromite and thinks that it's a bot:
I think it's probably because the viewport size given to the website is not the correct one of the device?
The text was updated successfully, but these errors were encountered:
Uh yes that could indeed be the case. Actually related to ScreenX/Y for mouse move, click etc. events
ScreenX/Y
Sorry, something went wrong.
https://github.com/uazo/cromite/blob/32fa8435523f71f1d2b6ac2facdea91e874c6904/build/patches/Viewport-Protection-flag.patch#L239
Though, this is a very rare case I think. Suppose some antibots would be willing to block users having that specific feature enabled.
=> good to know, but probably not as relevant?
What do you think of doing an exception for mobile users only?
Something like:
if(e.pageY == e.screenY && e.pageX == e.screenX && !navigator.userAgentData.mobile){var score=1}else{var score=0};
What do you think of doing an exception for mobile users only? Something like: if(e.pageY == e.screenY && e.pageX == e.screenX && !navigator.userAgentData.mobile){var score=1}else{var score=0};
Maybe a better score, year. Even though arguably - the score calculation isn't implemented properly anyways.
No branches or pull requests
Hello,
Cromite a popular fork of chromium with many privacy features, has a feature called "viewport size protection". The feature is added through this patch: https://github.com/uazo/cromite/blob/master/build/patches/Viewport-Protection-flag.patch
When this feature is enabled, brotector detects some odd behavior from cromite and thinks that it's a bot:
screen-20241205-231140.1.mp4
screen-20241205-233102.mp4
I think it's probably because the viewport size given to the website is not the correct one of the device?
The text was updated successfully, but these errors were encountered: