This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I notice a rather annoying problem with Excel 2016 - when scrolling using either a trackpad or mousewheel, the scrolling is not at all smooth. Instead, the scrolling is very jumpy. By jumpy, I don't mean that the scroll will go from point A to point B in a snap rather than a smooth motion. Rather, when initiating a scroll, the spreadsheet will sort of vibrate and bounce rapidly back and forth before the scrolling commence. The problem is particularly obvious when scrolling horizontally, and it sometimes won't scroll at all, no matter how many times I try. In such instances, the only way to move around the spreadsheet is either the arrow key or by clicking on the scroll bar. Sometimes initiating a scroll would cause a beachball to appear for a sec or two, and I'm on a Quad core 2012 Retina Macbook Pro. This is a persistent problem and has not be fixed in the last Excel update. This is also not a machine dependent problem, because I experience the same scrolling problem on my 13" Retina Macbook Pro as well. Anyone else having this issue?
A comprehensive suite of productivity tools and cloud services that enhance collaboration, communication, and efficiency. Combining classic Office apps with advanced Microsoft 365 features, it supports both personal and business needs
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
So sad :-(
At least I realise that this is not my imagination.
It's horrible.
Hope they help it soon.
Sorry, yes - keyboard repeat rate doesn't appear to affect the mouse wheel scrolling. It influences the scrolling with the arrow keys, which has always been crappy as well.
Mouse wheel scrolling - which I use much less often - actually appears to be slightly improved for me in this latest version. It's still a bit scrappy and juddery, but less so than it was. I also note that the scroll bars no longer look a total mess if you have them set to always be displayed. So there is hope.
Scrolling with the keyboard still awful though! And that damned cursor movement smoothing is still there. Never thought I'd actually want to use OpenOffice Calc rather than Excel... but Excel for Mac is doing its best to try to persuade me ;)
--Tom
I've tried changing the mouse wheel scroll speed and acceleration using the default drivers, SteerMouse and the Logitech Control Center - all to no avail. I don't understand how the keyboard repeat rate would affect mouse scrolling. But even it if does, you shouldn't have to tinker with setting like this to get proper behavior. Scrolling worked just fine in all previous versions of all Excel, there is no excuse for the current mess - and even less excuse for allowing the problem to linger for so long.
Thx for getting into this, Tom. It's a big bummer as i have o work on large sheets for clients. Scolling is pain in the... and i really think about getting back to Office 2011 installation instead of the subsciption.
Alex
Well it looks as if they are still working on it, because I've got 15.17, and the scrolling is, if anything, worse.
One thing that did occur to me is that keyboard repeat rate could be a factor, and after some experimentation it looks as if the scrolling behaves properly with a slow keyboard repeat rate. (I've no idea which setting is the default; I've always just set it to the fastest one.) Perhaps this is what the Excel developers have been testing with, and another row needs adding to their test checklist...
I've sent them (yet) another sad face bug report, this time pointing out that perhaps they need to tweak the keyboard repeat rate to see the problem. So we shall see.
--Tom