Bug 1486705
| Summary: | [UPSTREAM] Wrong hover view after selecting Block Storage Manager | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Yadnyawalk Tale <ytale> | ||||||
| Component: | UI - OPS | Assignee: | Greg Piatigorski <gpiatigo> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Yadnyawalk Tale <ytale> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.9.0 | CC: | dajohnso, dclarizi, hkataria, jhardy, mpovolny, obarenbo, ytale | ||||||
| Target Milestone: | GA | Flags: | ytale:
automate_bug-
|
||||||
| Target Release: | cfme-future | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | ui | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-05-02 22:18:01 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | Bug | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | CFME Core | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Comment 1
Greg Piatigorski
2017-09-26 21:38:45 UTC
Created attachment 1331235 [details]
Storage Block Managers menu
Please dvise on how to recreate this problem. TIA.
Can you please provide a screen shot pointing where exactly hover view text on the page is missing and should be? TIA So far unable to reproduce in upstream, please see attached screen shot. Created attachment 1331474 [details]
Storage => Block Storage => Managers menu hover background
I know about the bug. But it's hard to fix. There are 2 menu items here handled by the same controller. Basically the 2 menu items lead to the very same page. Block vs Storage. There's no way to handle that correctly in the codebase. No simple fix. The best thing to do would be not doing that. NOT having 2 menu items pointing to the same place. That can be done by removing one of those from the menu. Not sure who can decide that. If that's not an option then a deeper analysis is needed and redoing of the way the active menu items are remembered. I consider that an overkill and would rather suggest speading up the move of this logic to the client. There's a plan to use Angular based Patternfly component for the menu. Then the logic would be on the client and the issue would disappear. |