You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a menu is evaluated as disabled, we disable it and prevent
the possibility to see its children by hover. However, there are some
issues with this:
- the user is mislead because we keep showing the arrow that suggest the
presence of children items
- the user can simply not navigate through the submenus to see what kind
of feature could be available
- if a menu has several children some of which are readonlyAllowed, then
the readonlyAllowed condition has to be set on the parent as well; the
'enabling' condition therefore becomes a combination set on both the
parent and children
- if a parent menu is computed as 'enabled' it will not be greyed out
(suggests that it has useful children) even if the said children are
not enabled.
This revision changes the computation of 'enabled' state of item by
looking at the full tree of children and applies the following logic;
A parent menu is disabled if every leaf of the tree is disabled. A
single 'enabled' leaf (that is a child without children of its own) will
make all its parent enabled as well, up to the root. We also allow all
submenus to be opened regardless of the state of the parent.
The user will therefore have a visual hint that there are active
submenus or not (if all children are disabled, so will be the parent)
and they will also have the possibility to have a look at all children
to explore the possibilities.
Task: 5331717
0 commit comments