Back button will be shown if either parentMenu or onBackButtonClick prop is specified on NavigationMenu

I wonder which should take priority. Right now if both parentMenu and onClick are specified in the NavigationBackButton then the parentMenu takes priority so the button will act as a back button to the parent menu.

It doesn't make sense to have both props specified, but parentMenu might act as an information. For example, when I'm creating menus it would be great to see what's the parent menu of the menu I'm creating. But I'd like to have a custom back button click handler.

IMO, onClick should take precedence. Or we can utilise the event.preventDefault().

<NavigationMenu
	menu="custom-back-click"
	title="Custom back button click handler"
	onBackButtonClick={ ( e ) => {
		e.preventDefault(); // This will prevent the default onClick handler which navigates to the parentMenu
		setActiveMenu( 'root' );
	} }
	backButtonLabel="Go back to root"
/>

Size Change: +31 B (0%)

Total Size: 1.17 MB

_{compressed-size-action}

I wonder which should take priority. Right now if both parentMenu and onClick are specified in the NavigationBackButton then the parentMenu takes priority so the button will act as a back button to the parent menu.
...
IMO, onClick should take precedence. Or we can utilise the event.preventDefault().

I also think that onClick should take precedence but not completely override it, since we might want to execute some side effects in it, and then continue with back navigation as usual (e.g. let's say someone wants to track stats for back button clicks in their component or similar). On the other hand, if someone wants a complete override of the behavior, they can optionally use event.preventDefault() as you've pointed out.

• onBackButtonClick will be called with the Event object. This way we can use event.preventDefault() to prevent the default behavior (navigate back to parentMenu)
• Rebased and added stories.