You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The title may be a bit confusing. Please find a GIF below,
Upon opening the launcher, hovering the mouse is tracked and the options are focused.
Even when I don't hover, before opening the launcher, if the mouse happened to be at a height that's adjacent to the launcher, it focuses that option automatically.
It leads to a bad experience for me because when I type to find, it focuses the intended option but then it focuses back on the option that's being focused by the cursor. It keeps on flapping until I manually move the cursor out of the way.
My setup,
OS/compositor: macOS 15.2
Wezterm version: Happening on both stable (20240203-110809-5046fc22) and nightly (20241205-083533-6f375e29).
I looked at the docs but didn't find any relevant options that would affect this behavior. disable_default_mouse_bindings also doesn't affect this.
I'm not sure if this is a bug or not so I didn't use the bug report template. Please let me know if any additional information is needed from my end.
The text was updated successfully, but these errors were encountered:
The title may be a bit confusing. Please find a GIF below,
Upon opening the launcher, hovering the mouse is tracked and the options are focused.
Even when I don't hover, before opening the launcher, if the mouse happened to be at a height that's adjacent to the launcher, it focuses that option automatically.
It leads to a bad experience for me because when I type to find, it focuses the intended option but then it focuses back on the option that's being focused by the cursor. It keeps on flapping until I manually move the cursor out of the way.
My setup,
20240203-110809-5046fc22
) and nightly (20241205-083533-6f375e29
).I looked at the docs but didn't find any relevant options that would affect this behavior.
disable_default_mouse_bindings
also doesn't affect this.I'm not sure if this is a bug or not so I didn't use the bug report template. Please let me know if any additional information is needed from my end.
The text was updated successfully, but these errors were encountered: