Menu Customizer - Inconsistent use of Tags and Format Menu Items

[monikarao]

When using the standard menu administration it does not display "Tags" and "Format" to add into menu items.
When using the menu controls in the customizer, it display "Tags" and "Format" options to appear as menu-items.

[monikarao]

Standard Menu in administration (No Tag, Format Option)

[monikarao]

Customizer Menu - Tag, Format Options displayed

[afercia]

@monikarao you may want to check the Screen Options in wp-admin/nav-menus.php, and see if Tags and Format are checked.
@westonruter shouldn't these Screen Options be synced in the Customizer?

[celloexpressions]

There is a screen option for this in the old admin interface (if we still haven't, we should really add a big warning there about using the customizer so that you can live preview, among other things).

These screen options are intentionally excluded from the customizer, due to the generally poor user experience of screen options. The nav menu item options were brought over as a prototype for "panel options" in the ccustomizer, although this pattern has not been used elsewhere in core. It was determined that options would not be necessary for taxonomies and post types, as the proper use of show_in_nav_menus when registering the post type or taxonomy would automatically handle this without individual user interaction (decisions, not options).

Unless there is a compelling argument to revisit that design approach, I suggest closing this ticket. I haven't seen any other suggestions for this yet, and the feature is several years old now.

[afercia]

Previously #33779.

Considering the difficulties faced to keep in sync the "advanced menu properties" (which are options based on similar checkboxes) between the Menu screen and the Customizer, I'd personally be in favor of keeping it simple. See #38952, #36202, #35273, #35112.

[monikarao]

@afercia Yes I've checked that screen options but it should synced in the Customizer.

[karmatosed]

The consensus was to close this, so I will follow through with that and close this ticket. Thank you, everyone who has worked on this. By closing this, it doesn't mean we can't reopen if more information comes to light, but quite some time has passed, so for now, I am moving this on with a conclusion based on the majority feedback.