Description of problem: Secondary and Tertiary Nav shows a left arrow that can not be clicked to collapse the nav on an inactive menu item. No icon should be visible when nav can not be collapsed. Also, should be displaying a pin rather than an arrow when it can be collapsed. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Open secondary nav menu that is not active 2. Attempt to click left-facing arrow in menu header 3. Actual results: Nothing happens Expected results: No icon should be displayed when menu item is not active Additional info:
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/740f8d8ae65b9ff83f37c7d9557aed80eb170808 commit 740f8d8ae65b9ff83f37c7d9557aed80eb170808 Author: Dávid Halász <dhalasz> AuthorDate: Thu Jun 9 10:51:58 2016 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Thu Jun 9 11:41:26 2016 -0400 Update markup for pin/unpin icons in the tertiary navigation The fontawesome classes are obsolete and can cause issues in the future. https://bugzilla.redhat.com/show_bug.cgi?id=1344412 app/views/layouts/_vertical_navbar.html.haml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
https://github.com/ManageIQ/manageiq/pull/9133
Can somebody provide me a screenshot with these non-clickable arrows and clickable arrows instead of pin?
Yes, I can see there are no arrows and only pins. But pins are only visible in menu item activelly used. I can't pin different menu items. When I want to pin different items I first must select them (make active) and then pin appears on that item. Is it designed to work like this?
That's correct. Only the active menu items can be pinned.
Okay, verified in 5.6.0.11. It's displayed as it should.
https://github.com/ManageIQ/manageiq/pull/7620
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348