[ https://issues.jboss.org/browse/GTNPORTAL-2814?page=com.atlassian.jira.pl... ] Viliam Rockai commented on GTNPORTAL-2814: ------------------------------------------ Current proposal has some flaws: * It doesn't work out of the box, that's why I'm showing only the commit not PR, I was waiting for the navigation API to be merged. For the same reason I didn't add the part to add the navigation portlet to the mobile layout. * There is a problem with collapsible container plugin in navigation portlet when the page is opened on small device which can be rotated so the screen CSS will change because of media queries and the container is always collapsed (because on the layout for small screens, the sum of children width is always more than the screen width - if 2 or more nodes are present). This can be resolved by investing more time into collapsible container plugin so it will work with responsive layout (with several problematic areas like em to px conversion) or by not using the plugin in this portlet at all and splitting the navigation into more lines. I would prefer not using it here, but using this implementation in the header portlet. * There are flaws in the navigation menu handling javascript: ** The menu is opening only to the right side, with some number of subnodes you won't be able to display them on screen. ** The menu handler (arrow) must be clicked to both open and close the submenu. ** On smaller screens, the submenu of the leftmost node (if any) is rendered outside the screen for some combinations of node-name string lengths. I suggest spending more time on the navigation menu JS to resolve the issues above and implementing it as a jQuery plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira