Add setting to force user to click on top level menu items to trigger the display of their corresponding menu items

[michaelrogers0]

Body

What are you proposing?

Add a setting to allow users to force themselves to need to actually click on top level menu items (such as "Zed", "File", "Edit", "Selection", etc) to trigger the display of their corresponding menus. Currently users do not need to click, they can just hover. I would recommend requiring the "click" to be the default, at least on any OS (such as Windows) where this is the norm.

Why does this matter?

This matters because hovering to activate a top level menu is an anti-pattern on Windows.

What problem does this solve?

It solves the problem of surprising Windows users by immediately showing the menus when hovering over them.

What becomes easier or possible?

It gets easier to avoid inadvertently triggering the display of menus. This is especially important because to dismiss those menus you do actually need to click.

[bbbbbr]

Came here searching for a solution to this.

Requiring a click to activate menus can help increase the accessibility by making the actions related to them more intentional and require less fine cursor control.

Some examples...

Avoid auto-showing the menu when they may not be intended and the cursor target is near enough to the menu that it is likely to result in accidental menu display. For example the "recent projects" button, which if you overshoot and hit the menu then becomes covered up by the menu.

Additionally, not auto-hiding an open menu when the mouse leaves it's focus area. That way, once again, if you over shoot then you don't lose the menu and have to start over with it.

These are established patterns across many UI toolkits and operating systems which users are familiar with and have stood the test of time with regard to usability.

[iamqiz]

Zed is really a strange editor, not only in terms of the way menus are displayed, but also in terms of the display positions of menu items, such as "About Zed"