feat(Button): added circle variant#7922
Conversation
|
Preview: https://pf-pr-7922.surge.sh A11y report: https://pf-pr-7922-a11y.surge.sh |
|
These buttons also need larger icons. We used A couple of ways I can think of doing it off the top of my head:
|
248ef90 to
b209e8d
Compare
|
@mcoker went the scale route for now, using 1.29 just to keep the value short and it's the closest to 18px (0.06 over, vs 1.28 scale being 0.08 under). |
| --#{$button}--m-circle--PaddingBlockStart: var(--pf-t--global--spacer--control--vertical--default); | ||
| --#{$button}--m-circle--PaddingInlineEnd: var(--pf-t--global--spacer--control--horizontal--compact); | ||
| --#{$button}--m-circle--PaddingBlockEnd: var(--pf-t--global--spacer--control--vertical--default); | ||
| --#{$button}--m-circle--PaddingInlineStart: var(--pf-t--global--spacer--control--horizontal--compact); |
There was a problem hiding this comment.
I don't think --compact is the right padding to use for the inline variants. While it gives you the correct spacer, it may not forever if we update the compact spacer to be something else.
Since the min-width will always make these buttons a square, I might just leave the inline spacers off? Or have them reference the top/bottom spacers? I would probably just remove them since the min-width's role is to make it at least a square.
|
🎉 This PR is included in version 6.5.0-prerelease.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
* feat(Button): added circle variant * Added aria * feat(Button): updated to beta * feat(Button): added circle styling to menu toggle * feat(Button): added scale to circle icon * feat(Button): updated inline paddings to 0 --------- Co-authored-by: Eric Olkowski <git.eric@thatblindgeye.dev>
Closes #7913
The small variant paired with circle buttons looks like it breaks the small styling and it would also break the large/CTA styling, let me know if we would want small and/or large + circle to have decreased/increased padding respectively