-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistent and configurable OK/Cancel buttons #240
Comments
Definitely don't change based on environment, it should be consistent. Otherwise you end up with different button order on desktop vs. phone for example which is disorienting. The choice of order doesn't really matter much IMO. There are good arguments for both directions and neither really wins out. I think the one thing that maybe tips it toward the Cancel/OK order is that when you have additional buttons in that row, the additional buttons go on the left, and then the Cancel and OK buttons are always in the same position. Minor point though. |
BTW it sounds like having OkButton and CancelButton components would probably be a good idea here. Thin wrappers around Button but it would simplify the customization and ensure consistent application of i18n and so on. |
That's interesting... and would make styling straight forward. |
Currently components like
DateRangeField
andMultiSelectField
have OK/Cancel or Cancel/Apply buttons...They should be...
variant
/color
defaults?fill
/primary
, and Cancel (secondary) bedefault
/default
, and allow it to be configured insettings()
Related:
The text was updated successfully, but these errors were encountered: