You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it's possible to create a menu and add it to itself when selecting the menu from the "Existing menus" dropdown.
I think this could be a minor bug since the backend seems to ignore the recursion, returns a 200 status, and the menu doesn't get broken.
Step-by-step reproduction instructions
Create a menu using the Navigation (beta) option in Gutenberg.
Click on the placeholder.
Click on the "Existing menu" dropdown.
Expected behaviour
If the user has several menus, the name of the current one shouldn't appear on the list. If this is the first menu, the dropdown shouldn't appear or at least it shouldn't contain the current menu as an option.
Actual behaviour
The list contains the name of the current menu.
Screenshots or screen recording (optional)
Screen.Recording.2021-04-12.at.15.01.10.mov
WordPress information
WordPress version: 5.7
Gutenberg version: 10.3.2
Are all plugins except Gutenberg deactivated? Yes
The text was updated successfully, but these errors were encountered:
Currently, it's possible to create a menu and add it to itself when selecting the menu from the "Existing menus" dropdown.
I think this could be a minor bug since the backend seems to ignore the recursion, returns a 200 status, and the menu doesn't get broken.
Step-by-step reproduction instructions
Expected behaviour
If the user has several menus, the name of the current one shouldn't appear on the list. If this is the first menu, the dropdown shouldn't appear or at least it shouldn't contain the current menu as an option.
Actual behaviour
The list contains the name of the current menu.
Screenshots or screen recording (optional)
Screen.Recording.2021-04-12.at.15.01.10.mov
WordPress information
WordPress version: 5.7
Gutenberg version: 10.3.2
Are all plugins except Gutenberg deactivated? Yes
The text was updated successfully, but these errors were encountered: