-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
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
Scrolling fails to function as expected using Google Maps #4617
Comments
@IdlePhysicist Can you try in brave://settings/system and turning off hardware acceleration to see if that changes the behavior? |
@rebron I use Brave with hardware acceleration turned off. |
Yesterday I turned on hardware acceleration on and raised shields, this fixed the smooth scrolling. But I have also tried to reproduce the error with an external mouse (HW acc. off) and it is not producible. This leads me to believe that there is some issue between the Mac's trackpad and Brave. |
@IdlePhysicist How is it working with hardware acceleration on and shields down? Any difference? I'm thinking this is a hardware acceleration issue only. |
@IdlePhysicist makes sense - we have a few other trackpad issues I believe... will try to find/link them |
@rebron Sorry it took a little while to get back to you. I can now confirm that Brave exhibits expected behaviour with hardware acceleration enabled, and shields down. |
I have a suspicion that this issue is caused by canvas fingerprint protection, and if it was spoofed instead of blocked (#5196), this wouldn't be an issue. I think this because I had used an extension to spoof canvas fingerprint in Chromium, and as far as I remember Google Maps worked smoothly (that extension is currently broken so I cannot easily verify). |
using Google's Maps is very choppy compared to Chrome, and even Safari .. and this is with HW accel turned on, and shield completely down for it. any other workarounds ? thanks ! |
This issue is still present. Tested with Brave v0.68.139 with macOS 10.14.6 - MacBook Pro (15-inch, 2017). But if you enable "Cross-site trackers blocked" and or "Device recognition attempts blocked" the jumping appears again. I hope this is helpful. |
Following fixed this issue / worked for me: 1. Enable Hardware AccelerationOpen this Setting or enter the following in the address bar:
2. Set Shield to block cross-site fingerprinting and cross-site cookiesTested on:
Hope this helps others. |
Since there haven't been concrete steps to reproduce and this has been open for a while, I'm going to close. Def suggest trying the work-around above 😄 |
For anyone who ends up in this issue and none of the other solutions are working, here is a short guide: First, try going to Google Maps in an incognito window. (File > New Private Window). If the scrolling is smooth there, then likely it's a settings issue, and you might be seeing the "lite" version of Google Maps. You can tell by whether 3D is available in Satellite view. If it's not, this YouTube video has 9 possible solutions. https://www.youtube.com/watch?v=n5skrIePo50 (For me, it was the 2nd solution that permanently fixed the scrolling bug in Brave.) |
Description
When I use Google Maps the two finger trackpad scrolling is hyper sensitive and makes zooming in/out impossible to use practically. This does not occur in Firefox, Chromium, or Safari.
Steps to Reproduce
Actual result:
Zooming/scrolling is hyper sensitive to movement on the trackpad. Makes for poor user experience.
Deactivating shields, allows for a better user experience, the zooming is somewhat less sensitive but it is still jumpy and not smooth compared to the other browsers mentioned above.
Expected result:
Smooth zooming like in the browsers mentioned above.
Reproduces how often:
Easily reproduced, this happens whenever I use Google Maps in Brave.
Brave version (brave://version info)
I am running Brave 0.64.77 on a Mid-2012 MacBook Pro with macOS Mojave 10.14.5
Version/Channel Information:
I only use the stable release and have not yet tested with the development releases.
Other Additional Information:
The text was updated successfully, but these errors were encountered: