Disambiguate "Automatically add new top-level pages to this menu." as being an option and not a menu location

[pbearne]

Hi all

A small UI patch

In the new customizer the option to "Automatically add new top-level pages to this menu." looks like its part of the menu location list.

I have added a patch to give this a title of "Menu Options" to separate it from the location list

Paul

[pbearne]

Patch to add "menu options" title

[celloexpressions]

+1. This previously had some spacing at least, but not currently. However, this also brings up that this needs to be a separate control, as it was previously, so that plugins can add controls before and after it or remove it.

[pbearne]

The menu without the Menu Options

[pbearne]

Screenshot with the "Menu Options" Title

[westonruter]

As noted in Slack, the auto_add property of the nav_menu setting can receive a separate control in the same way that a separate control has been added for the nav menu's name: ​https://github.com/xwp/wordpress-develop/blob/556ec207f12da71aca788a1d3d98b317c97407d9/src/wp-admin/js/customize-nav-menus.js#L1577-L1621

So a nav_menu[...][auto_add] control would be added with a linkage to the nav_menu[…] setting, but the element would just sync with the auto_add property.

[pbearne]

@afercia should this have an aria tag?

[afercia]

Replying to pbearne:

@afercia should this have an aria tag?

@pbearne hi, I think no. Have something specific in mind? I think it needs something more semantic than a span, though. Looking at this, the menu locations checkboxes are logically grouped so maybe "Menu locations" should be a legend of a fieldset that groups the checkboxes.
About the "Automatically add..." checkbox, it's a bit difficult since it's just 1 checkbox and there's nothing to actually "group" together. Agreed that should be separated from menu locations options since logically has a very different meaning.

[valendesigns]

I can work up a patch that adds a new control for auto_add.

[obenland]

@valendesigns any news?

[valendesigns]

Patch 32820.diff​ adds a new nav_menu_auto_add control to the end of the menu and I've tested that it actually adds top level pages. If there are any text changes that need to be made let me know. As it is now the new control looks like Capture.2.PNG​.

[celloexpressions]

Patch looks good to me (untested though). My only suggestion would be to add a reference to #30741 in the todo comment about the control container code.

[westonruter]

In 33189:

Customizer: Disambiguate a menu's auto-add pages option from preceding menu location checkboxes.

Creates a separate nav_menu_auto_add control type following the pattern of the nav_menu_name control type.

Props valendesigns.
Fixes #32820.

[ocean90]

<span class="customize-control-title"><?php _e( 'Menu Options' ); ?></span> shouldn't be inside the label element and we should capitalize locations in Menu locations too.

Not sure about making Menu Options a part of the new control since you can remove and add more options, see comment:2. Thoughts?

[valendesigns]

I'm not exactly partial to that title either, as it's to ambiguous. Though If we remove the title completely nothing was achieved visually. Things would look exactly the same as before so maybe we parity the Admin Menus a bit more and use 'Auto add pages'. So we get some visual separation here.

If we go one step further and give the same treatment to add & delete in the section above. Then we could order it title, items, add, auto add, locations, delete and then we would more closely be mimicking the UI in Admin Menus.

Or should we just change the title to 'Auto add pages' and call it good?

[pbearne]

Part of the thinking to breaking this out was to allow "other options" to be added to the new control via action and filters

Otherwise, we could of stay with the just adding titles.

So I guess the question is is it possible to make the control extentable?

Paul

[valendesigns]

@pbearne Where in the description or comments does it mention or imply this issue has anything to do with actions and filters being applied inside the control?

[celloexpressions]

@pbearne the point of making this a distinct control is that it offers more flexibility with manipulating the UI here via the Customizer API than you could get via traditional actions and filters. See WP_Customize_Manager::add_control(), get_control(), and remove_control() for ways to add additional controls here, modify the auto add control, or remove the auto add control.

I think it's fine to say menu options by default, and plugins can remove/change that if they need to. A plugin that adds another basic checkbox control below the auto-add option would work perfectly with the current setup, though. I also think @nacin would probably prefer that we use Menu locations and Menu options for the capitalization, although I'd say it works either way as long as they're consistent.

[valendesigns]

Moved the title out of the label and standardized the capitalization in 32820.2.diff​.

[westonruter]

In 33317:

Customizer: Move "Menu options" heading outside of a nav menu auto-add control's label.

Standardizes capitalization. Amends [33189].

Props valendesigns.
Fixes #32820.