Inconsistent mouse scroll wheel behavior on hover depending on buffer type about nyxt HOT 5 OPEN

Makes sense.

I want what you propose:
scroll the buffer being hovered!

from nyxt.

Eeeeeew a bug

from nyxt.

Soo... just thinking out loud here.

If we set the input-focus to follow mouse pointer hover position,

• then this scrolling problem is fixed, as well as a few other problems (like trying to run quit-prompt-buffer when focus is on the main buffer).
• however, we introduce another problem (opening prompt buffer with mouse pointer on the upper half of the screen would change input to main buffer at the wrong time)

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.)

from nyxt.

Like this:
a mouse cursor transition from mainb → promptb | toggle-buffer-focus
a mouse cursor transition from promptb → mainb | no action (a click is still required)

from nyxt.

@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:

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.

I think it's clear what my choice would be :)

from nyxt.