Skip to content

Keep menu results responsive to touch without pointer motion - #741

Open
marksverdhai wants to merge 1 commit into
abenz1267:devfrom
marksverdhai:fix/touch-menu-hit-testing
Open

marksverdhai wants to merge 1 commit into
abenz1267:devfrom
marksverdhai:fix/touch-menu-hit-testing

Conversation

@marksverdhai

Copy link
Copy Markdown

Touch-only dmenu users can lose item activation after the query changes or keyboard navigation: disable_mouse() turns off GTK hit testing for the result list, and only subsequent pointer motion restores it. This also affects successive Omarchy submenus.

Add opt-in touch_mode = true to keep results targetable. The default remains false, and explicit disable_mouse still takes precedence. This preserves GTK's single-tap activation and swipe scrolling without changing menu actions or layouts.

Validation: the configuration opt-in/opt-out test passes, formatting and diff checks pass, and the same simulated Linux touchscreen tap returned no selection before the fix and the intended second item afterward. A swipe produced no accidental activation, then a tap selected item 7. A single touch also opened the Learn submenu in the real Omarchy menu.

Fixes #740.

@abenz1267
abenz1267 changed the base branch from master to dev September 13, 2026 08:24
@abenz1267

Copy link
Copy Markdown
Owner

can you fix the conflicts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Touch-only dmenu activation requires pointer motion because results lose can_target

2 participants