Frontmatter
| id | 3998 |
| title | button.Base: UI variations |
| state | Closed |
| labels | enhancement |
| assignees | [] |
| createdAt | Feb 6, 2023, 4:59 PM |
| updatedAt | Feb 6, 2023, 10:49 PM |
| githubUrl | https://github.com/neomjs/neo/issues/3998 |
| author | mxmrtns |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Feb 6, 2023, 10:49 PM |
button.Base: UI variations

tobiu
Feb 6, 2023, 10:49 PM
Hi Max,
this took quite a while. Let us create a follow up ticket for the ghost ui.
we most likely also need pressed states for our different button uis:
https://m2.material.io/design/interaction/states.html#usage
also a follow up ticket if needed. Let's do a quick call tomorrow.
tobiu closed this issue on Feb 6, 2023, 10:49 PM
Following up on #3996
In order to cater for different UI needs, I suggest splitting up the CSS variables for buttons into 'Base'(values that should be the same across all different button types) and 'UI Variants' like Primary or Secondary.
Base
Primary
:hover
:active
Disabled
The same variable structure would be needed for the following UI button types: