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
When we create a new navigation block, the default navigation we use is the most recently created one. Sometimes this might not be the best option.
For example, if a user creates a header navigation and then a footer navigation, and then switches theme, the new theme will use the footer navigation in all navigation blocks.
What is your proposed solution?
Instead, if the block doesn’t have a menu assigned the fallback algorithm should pick the one that is most relevant to the Template Part within which the block resides.
The text was updated successfully, but these errors were encountered:
Hi folks,
We are only one week away from the Beta 1 cut-off date for WordPress 6.6. This issue hasn’t seen any movement in a while, so we (the editor triage leads of the 6.6 release) have decided to remove it from the WordPress 6.6 Editor Tasks project board.
What problem does this address?
When we create a new navigation block, the default navigation we use is the most recently created one. Sometimes this might not be the best option.
For example, if a user creates a header navigation and then a footer navigation, and then switches theme, the new theme will use the footer navigation in all navigation blocks.
What is your proposed solution?
Instead, if the block doesn’t have a menu assigned the fallback algorithm should pick the one that is most relevant to the Template Part within which the block resides.
The text was updated successfully, but these errors were encountered: