Currently, triggeredById returns as null when a JSquery is triggered by one of the navigation component options, which makes it nearly impossible to deploy in a user friendly manner. It would be great if the menu options had both label AND value inputs so that a single JS query could be written to handle the context of the click. Additionally, you can't close the navigation menu (when it is condensed to a 2-column width) with javascript, which doesn't make for a great user experience because you have to manually click the icon to close it. The tabs component is great for navigation and works about as well as the navigation component, so there is a work around but the dropdown menu style is really clean looking and could be a nicer component for navigation once there is a little more usability around it