John E Vincent created CLOUDSTACK-6310:
------------------------------------------
Summary: Consider removing (or at least an option to disable)
pop-over functionality in the UI
Key: CLOUDSTACK-6310
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6310
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Reporter: John E Vincent
One of the most painful things in the CS UI is the "pop-over" functionality.
To date it has caused countless unintentional behaviours on our part and from
what I've gathered to other users as well.
There are a few main issues:
- The firing of the popover UI happens inconsistently.
In some cases it fires mousing over a menu item. In other cases it fires when
mousing over a "+" sign in lists. Still in other cases it seems to fire when
you hover for some undetermined period of time in a list item. I'm pretty sure
this is all latency related but I haven't looked at the code to see if the UI
popover triggers a new API call for details.
- The pop-over doesn't clear properly all the time
This one is really annoying because depending on the variable size of the
popover and where it fires, it actually OBSCURES the list you're trying to
navigate.
- The pop-over doesn't reset for different elements
This is similar to the previous and actually the cause of much consternation.
You can mouse over the "+" for a list item and it will actually be showing the
WRONG item. This can be disastrous on the same scale as the "reset/reboot" icon
fiasco.
- The information never fits anyway
In almost every non-trivial case, the popover can't hold the information it
needs to display anyway.
I want to be clear that I really enjoy the UI in most cases but the popover has
caused me countless amounts of lost time in trying to avoid it only to have it
get stuck or fire just because I moved the pointer out of the way.
I don't have any hard suggestions here and I'm not a UI expert by any stretch
but it feels to me that possibly an accordion approach (expand down on list
item click for instance) would be a much more navigable paradigm. This brings
back the intent of selection with UI interaction instead of it being subject to
where someone stows the mouse pointer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
