Do we need command=show-menu and command=hide-menu?

[josepharhar]

Right now we have three menu commands:

1. command=toggle-menu
2. command=show-menu
3. command=hide-menu

In theory the difference between toggle-menu and show-menu is that toggle-menu can close submenus when it is activated, but I am removing part of the closing functionality from toggle-menu in order to implement the resolution about moving focus into a submenu, and the only remaining difference is that toggle-menu has interest invoker behaviors.

When I was making a demo with this feature a week ago, I mistakenly thought that show-menu was the preferred way to make submenus, and I should have used toggle-menu. I was surprised when it didn't work as expected. With this in mind, I think it would make sense to remove show-menu and just have toggle-menu.

Similiarly, I don't see a great use case for command=hide-menu. The only really valid thing I can think of is to have a menuitem inside of a menulist which closes the menulist, but I've never seen such a thing in any application.

Can we just remove command=show-menu and command=hide-menu to save developer confusion about how to create menu elements?

[lukewarlow]

I think this is fine? show-menu especially seems pointless but perhaps for buttons rather than menu items it makes more sense?

[scottaohara]

youtube has instances of menus (settings cog for a video) where only one menu list is shown at a time, and a "back" control exists which would make sense as a menuitem that hid the current menu to reveal the prior menu.

i mean.... in both the invoking.of a sub menu and the backwards navigation to get to the prior menu, there's an argument to be made that maybe the back controls aren't "hide" but "show" for the prior menu popup? it's just weird to think of them as toggles, since it both opens the sub menu or higher-level menu and closes the one the user is attempting to leave. ... ???

the actual implementation of the youtube menus dont' follow the above though, they're weird hodge podges of buttons and headings and menuitems, and tbh it behaves rather poorly with VoiceOver running. so, however this ends up, hopefully it's nothing like that behavior :(

[css-meeting-bot]

The Open UI Community Group just discussed Do we need command=show-menu and command=hide-menu?, and agreed to the following:

• RESOLVED: move show-menu and hide-menu commands to v2

The full IRC log of that discussion

<masonf> q+
<jarhar> proposed resolution: move show-menu and hide-menu commands to v2
<dgrogan> +1
<masonf> +1
<scott> +1
<dbaron> +1
<jarhar> RESOLVED: move show-menu and hide-menu commands to v2
<Jacques> +1 I'm always in favor of deferring things that can be added later.
<dgrogan> +1 to Jacques

[mfreed7]

The Open UI Community Group just discussed Do we need command=show-menu and command=hide-menu?, and agreed to the following:

Actual meeting notes are here: https://docs.google.com/document/d/1mHzKRTGk6bs7uHN9Y3HuN3mT-XFd7mBP7tLlWNPnyOs/edit?tab=t.srm6ztuhp2gh

[dbaron]

Also there was some previous discussion on this topic in #1326.