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
Users are finding the extension and profile checkbox in the current UI to be confusing.
The behavior of the profile checkboxes changes on different pages:
On listing pages (Categories, Classes, Objects) it filters down to items that refer to the profile
On detail pages (Object and Class pages) it adds the attributes defined by the profile
Checking a profile on one page, for example Categories, then to another, for example Objects, can unexpected lead to the second page being empty.
The filtering dropdown on the Dictionary, object, and class detail pages are conceptually the same, though with a different UX -- perhaps unnecessarily different UX.
The left gutter where these checkboxes are placed disappears when the browser window is too narrow, and it missing on mobile (specifically on the iPhone). Worse, when the gutter is missing, the functionality is unavailable.
A better solution would be to have a profiles dropdown with multi-select, as we have with the Class and Object details pages (.e.g that dropdown is mixed use, with line separators).
I would not add more to the mix but have a separate Profiles list box in each place:
For Categories, to the left of the Search box, when selected it filters the classes as today.
For Classes and Object listings, to the left of the Search box, it filters classes and objects that support the profile
For Class and Object detail pages, to the left of the Items Selected box, it adds the attributes defined by the profile
The downside to this approach is that the top of the pages scroll off, and the list boxes with it, while today the left column/gutter stays visible. If we could freeze the header section on list and detail pages, it would alleviate a number of usability issues. IMO.
Users are finding the extension and profile checkbox in the current UI to be confusing.
Related issue: #44.
Solution(s) TBD.
cc: @pagbabian-splunk
The text was updated successfully, but these errors were encountered: