Excel scrolls the wrong window on hover

Anonymous
2016-02-19T13:07:31+00:00

If two (or more) instances of Excel are open, and one of them has the focus, when hovering the second one, scrolling is still applied to the first one. We need to steal focus from the first window of Excel and then scroll the second.

This seems like a bug and can be reproduced easily (more easily with two monitors).

Lets say you have two windows of Excel open : A and B.

You're working on A but you need to read B. hover your mouse over Excel B, scroll... the scrolling occurs in A ! You must click on B, scroll, then return on A.

Now, with focus on A, open another application (let's say Word), and, of course, set the focus to the newly open app. Be sure to see Excel A and B. Hover your mouse over B, scroll... Scrolling still happens on A.

This does not happen with Word or Outlook. If you open 2 windows of Word, the scroll occurs in the one that is hovered, as expected.

I don't think there's a solution, this is a bug and should be adressed by Microsoft.

Microsoft 365 and Office | Excel | For home | Windows

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.

0 comments No comments

46 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-12-05T16:46:48+00:00

    According to u/jenmsft (microsoft employee) at reddit windows 10 forum it is indeed this bug.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-05T16:35:18+00:00

    Fixed in insider build 17040. Now we just have to wait for it to be passed into the main release.

    See the link below:

    https://blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/

    The blog at the other end of this link does mention a scrolling bug that is addressed in the next build but is so vague that it could resolve the issue described on this thread or some other similar bug.  Hopefully (A YEAR LATER) Microsoft has resolved this.

    Was this answer helpful?

    0 comments No comments