[wp-trac] [WordPress Trac] #13273: Allow "'non-clickable" menu items
WordPress Trac
noreply at wordpress.org
Tue Sep 2 15:38:47 UTC 2025
#13273: Allow "'non-clickable" menu items
---------------------------------------+--------------------------------
Reporter: stgoos | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: 6.9
Component: Menus | Version: 3.0
Severity: normal | Resolution:
Keywords: needs-design dev-feedback | Focuses: ui, accessibility
---------------------------------------+--------------------------------
Comment (by joedolson):
I like the idea of adding a new object type that can be treated
differently; it might make implementation easier.
However, I still think that there's a lot to figure out in this. What the
object might become is going to depend on where it is in the menu - on the
top level, it would need to be a `button`, within a menu it might need to
be something else entirely, and that could depend on whether it's a parent
within the submenu or not.
Thinking about implementations, in a submenu it could either need to be a
heading or a trigger to expand another submenu.
While I'm intrigued by this, I'm wondering whether it's practical - it's a
lot of work to implement, and in the meantime the block editor will be
moving towards a more significant mega menu editing option.
This would provide something for classic themes, but there are already
many different solutions for the problem out there. Before we can really
start implementing, we'd have to have some clear ideas of what this is
going to accomplish.
Are we aiming to enable mega menu structures within the classic menu
editor, but without the scripting to control them, or are we going to be
more conservative about what options the settings allow?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/13273#comment:30>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list