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
{{ message }}
This repository has been archived by the owner on May 2, 2024. It is now read-only.
The person context menu disappears when the user chooses the default black color for a role. The triple dot context menu is visible for all other colors.
Make dots white when role is black label
Design -
Recommend either
(useful UX)
change triple dot to another color (white) when role color is black, or
not allow black as a role color (maybe a gray instead of black?), or
(less useful UX)
change default color to something other than black and hope no one ever chooses black, or
after the user clicks save, change the color chosen behind the scenes so that although black can selected, that selection can never be saved to the database, or
On discovering that a user has chosen black as a role color, show an error screen indicating that the PeopleMover has been compromized, and that the user should reboot their machine as a preventive measure, or
... (trying to stretch my mind to come up with something even more innocuous but insidious sounding)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The person context menu disappears when the user chooses the default black color for a role. The triple dot context menu is visible for all other colors.
Make dots white when role is black label
Design -
Recommend either
(useful UX)
change triple dot to another color (white) when role color is black, or
not allow black as a role color (maybe a gray instead of black?), or
(less useful UX)
change default color to something other than black and hope no one ever chooses black, or
after the user clicks save, change the color chosen behind the scenes so that although black can selected, that selection can never be saved to the database, or
On discovering that a user has chosen black as a role color, show an error screen indicating that the PeopleMover has been compromized, and that the user should reboot their machine as a preventive measure, or
... (trying to stretch my mind to come up with something even more innocuous but insidious sounding)
The text was updated successfully, but these errors were encountered: