IDS Enhancement Requests
Attached is merely a suggestion. This is open for discussion and testing.
Based on several user tests and interviews within FSM, we've found there's a level of hesitation or confusion over the secondary button colors. Users either don't know that grey buttons are not disabled, or are confused that a disabled button does not work. I've attached a proposed color change to the button states to help better convey Enabled vs Disabled.
Hey All,
Thanks again for this submission. As a result of this discussion, we have decided to alter the secondary button status to be an outlined version of the primary button, as you can see in the attached image.
This issue is currently slated for development as part of the 4.71 release. Progress can be followed here: https://github.com/infor-design/enterprise/issues/6977
I created a ticket last year for a similar request. Please see it here: https://jira.infor.com/browse/UXD-3692
Please consider the use case: there are multiple actions on the same screen with action hierarchy.
Thanks for submitting an Infor Design System enhancement request!
The IDS product team reviews enhancement suggestions on a regular basis and implements enhancements based on assessed value. If more information is required, an IDS Product Management team member will contact you for clarification.
I also agree Calvin's suggestion.
Another strategy is don't use filled gray for 2ndary. For example, maybe use Azure 6 border instead of fill with black text -- still less prominent than primary. Or border with Azure 1 fill. Etc.
Gray is more often associated with the disabled state.