Currently, the automation peer of RadNavigationView (RadNavigationViewAutiomationPeer) tries to create the automation peer for the element set as direct value of the Content property. This means that if the direct Content is a Grid or another element without an automation peer, the automation chain for elements deeper in the Content's hiearchy will break. 

Add logic that searches deeper in the Content's hierarchy to try finding the first element with an automation peer.

Sub-items of the parent RadNavigationViewItem instances could disappear when changing the view mode of RadNavigationView.

We could include a separator item to separate certain items from one another.

When the selected item is changed, its content will be unloaded. This can be a performance hit when each navigation view item have a large number of elements inside its content. 

Hello,

Currently when resizing the application, we get a scrollbar like this (which is not the best user experience):

 

We would like to have a "more" icon to show hidden items in a submenu.

 

Best regards,

Hello,

Currently when we start the application, no item is selected. Once we select one it appears as selected and we show a related pane. This is the nominal behavior of the component.

But we want to deselect it when we are clicking again on it (like in Visual Studio Code). So ideally we want a NavigationItemBehavior property with a value "Normal" and a value "Toggle".

 

Regards,