-
-
Notifications
You must be signed in to change notification settings - Fork 409
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
Inconsistent mouse scroll wheel behavior on hover depending on buffer type #3111
Comments
Eeeeeew a bug |
Soo... just thinking out loud here. If we set the input-focus to follow mouse pointer hover position,
Sooo... Can we set the input-focus to follow the mouse pointer -- AFTER a transition has been made (from main-buffer to prompt-buffer, but not the other way.) |
Like this: |
@lansingthomas think about the user. You suggestion feels overly complicated for no good reason. Generally speaking, setting the focus without a mouse click is rather unintuitive and not a good default. On the other hand, people expect to interact, i.e. scroll, with the thing that they're pointing to. Think about the text box from where you'll be writing a reply to my message. Hover over the box - it scrolls the message. Hover outside the text box - it scrolls the issue's page. Focus on hover is orthogonal to this discussion. From my top post:
I think it's clear what my choice would be :) |
Makes sense. I want what you propose: |
@aartaka look! the thing we talked about already has an open issue. I totally forgot about this... and made a new video describing the bug. |
scroll-buffer-up-down.mp4 |
Scroll on hover is hard, because GTK treats the view with focused input (which prompt buffer is) as the highest priority one. So we either focus out of prompt buffer (by clicking on main buffer or elsewhere), or do some infernal magic to unfocus on hover. |
With regards to focus, there seems to be deeper issues so this one can only be addressed after #1463 (comment). |
When hovering over the main or panel buffers, mouse scrolls are intercepted in the hovered buffer.
When the prompt buffer is open, mouse scrolls are intercepted exclusively by the prompt buffer.
The behavior is illustrated below.
simplescreenrecorder-2023-08-01_18.48.41.mp4
This seems to contradict the behaviour most users expect.
When the prompt buffer is open and the mouse hovers over a non prompt buffer area, I'd suggest either no scrolling or scrolling the buffer that is being hovered.
When the prompt buffer is open and the mouse hover over it, it should scroll it.
The text was updated successfully, but these errors were encountered: