-
Notifications
You must be signed in to change notification settings - Fork 40
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
fix: card push fee staking pool visual style #1933
base: main
Are you sure you want to change the base?
Changes from 2 commits
315806f
dc79db0
a5d1a3f
c19958e
5a13058
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Instead of changing Button in design component. Change the Button here In line no. 819
Add this and then try. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hello @abhishek-01k I reviewed the code again and noticed that, since block internally applies width: 100%, this behavior makes the button occupy the entire width of the container as a single element. However, in a flexbox container with multiple elements, this causes overflow, as each button tries to take 100% of the container's width. For this reason, I believe the best options to address this problem are: Op1: Using styled-components inline css: css={css`flex: 1;`} Op2: Supporting the flex property (instead of my previous change ${({ flex }) => flex && flex: ${flex};} Op3: Or creating a wrapper for the buttons, similar to the StakingToolTip component. <StakingToolTip >
<Button />
<Button />
</StakingToolTip > Based on this, to keep the component reusable, maintain more precise control over the design, and preserve adaptability, I would personally suggest extending the component to support the flex property (Option 2). Therefore, I would like to confirm which of these options you would prefer me to adopt. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hey @wolfcito, Yeah you are right about using block. It would create overflow issue. I think right now go with Option 1 because we are still working on Design system components and we will extend the property of Button to support flex property as well. Thanks for pointing out the issue. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hello @abhishek-01k , It's done! I have made the adjustment to the Push and Uniswap cards. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hello @rohitmalhotra1420, I hope you'll have a chance to review it. 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We cannot add this here as this will affect Button Design which is used in other places.