We removed the ability for that because of interactive elements nested inside a link accesibility violation. The clickable arrow icon (i) lives inside a NavLink. Nested interactive elements (-like behavior inside ) are problematic for screen readers and keyboard users, and are generally discouraged. Still, if you believe this is a must for your app you can set custom Template with desired behavior.