You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(27140): fix styles for Slippage Tolerance Button Group in Transaction Settings Modal (#29246)
This PR aims to fix a broken visual display for Slippage Tolerance
Button Group in Transaction Settings Modal.
After inspecting the styles for `ButtonGroup`, which is the component
applies to this part of UI, has overwritten issues of styles between
`button-group__button` and `radio-button`. Hence the solution is to
specify css based on variant more clearly and avoid the overwrite
problem.
<img width="321" alt="Screenshot 2024-12-16 at 18 59 19"
src="https://github.com/user-attachments/assets/09a9cce7-a308-4049-a0c6-a001659c301e"
/>
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->
## **Description**
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
[](https://codespaces.new/MetaMask/metamask-extension/pull/29246?quickstart=1)
## **Related issues**
Fixes: #27140
## **Manual testing steps**
1. Click "Swap" from the home screen.
2. In the swap interface, click the cog icon in the top right to open
the transaction settings modal.
3. Observe the slippage tolerance button group—it's visually broken.
## **Screenshots/Recordings**
<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->
### **Before**
<img width="339" alt="1"
src="https://github.com/user-attachments/assets/187e1024-0c0c-42fd-9fda-bc72725a7483"
/>
<!-- [screenshots/recordings] -->
### **After**
<img width="766" alt="Screenshot 2024-12-16 at 19 19 04"
src="https://github.com/user-attachments/assets/ee4f1eb5-ee47-4ac0-aaee-df65b7346cae"
/>
<!-- [screenshots/recordings] -->
## **Pre-merge author checklist**
- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.
## **Pre-merge reviewer checklist**
- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
0 commit comments