-
Notifications
You must be signed in to change notification settings - Fork 5.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 in Chrome slows to a crawl #401
Comments
I'm running Chrome 15.0.874.92 beta-m and my mouse wheel scrolling is too slow. I mean it is like two lines per step and it takes way too long to scroll a document, whereas my Windows 7 native scroll wheel step is 8 lines, which works elsewhere in Chrome but not in this editor? Though I don't see any gradual deteriorating as you suggest, it seems as if the editor overrides the stepping to two lines which makes it slow. One shouldn't really tamper with the OS scroll wheel stepping -- it's heresy! |
This behavior happens also in the latest builds in an Adobe AIR 3.0/3.1 environment (also webkit). |
Commenting out these lines fixed my problem in AIR:
Although... scrolling appears to be jerkier now? Hmm.... |
Having this problem in both Chrome and Safari. Same behavior as originally reported: scrolls normally for a while, then slows to an absolute crawl. (In Safari it does take noticeably longer to trip though.) Also perhaps worth noting is that when it flips into super-slow-mode, the trackpad scroll also slows to a crawl. Chrome 18, OS X 10.7. |
I haven't seen this in a very long time. If anyone is still experiencing this, let me know and I'll re-open it |
After scrolling up and down in a document for a few seconds, the scrolling suddenly slows to a crawl. However, the CPU usage looks normal and I can grab the scrollbar itself and move it around quickly. So I suspect this isn't a performance issue, but one related to the scroll detection and possibly inertia.
Chrome 13 on OS X Lion. Tested FF and it works fine, no scroll issues there.
@Gissues:{"order":52.795031055900836,"status":"backlog"}
The text was updated successfully, but these errors were encountered: