Skip to content
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

[Bug]: Reject and Confirm buttons on redesigned Signatures are not fully visible when using larger font size #13516

Closed
sleepytanya opened this issue Feb 14, 2025 · 3 comments
Assignees
Labels
area-accessibility Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking team-confirmations Push issues to confirmations team type-bug Something isn't working

Comments

@sleepytanya
Copy link
Contributor

sleepytanya commented Feb 14, 2025

Describe the bug

Buttons in redesigned signatures on both platforms are not fully visible when larger font size is used.

Expected behavior

Buttons are fully visible and easily accessible

Screenshots/Recordings

signatures.mp4

Android:

Image

iOS:

Image

Steps to reproduce

  1. Change font size in device settings
  2. Trigger signature

Error messages or log output

Detection stage

On main branch

Version

7.41.0 (1557)

Build type

None

Device

Samsung S24 Ultra, iPhone 16

Operating system

Android

Additional context

No response

Severity

No response

@sleepytanya sleepytanya added regression-main Regression bug that was found on main branch, but not yet present in production Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking team-confirmations Push issues to confirmations team type-bug Something isn't working labels Feb 14, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Feb 14, 2025
@metamaskbot metamaskbot added regression-develop Regression bug that was found on main branch, but not yet present in production and removed regression-main Regression bug that was found on main branch, but not yet present in production labels Feb 14, 2025
@jpuri jpuri self-assigned this Feb 14, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Feb 14, 2025
@sleepytanya sleepytanya added regression-RC-7.41.0 Regression bug that was found in release candidate (RC) for release 7.41.0 release-blocker This bug is blocking the next release Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking and removed regression-develop Regression bug that was found on main branch, but not yet present in production Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking labels Feb 15, 2025
@sleepytanya sleepytanya changed the title [Bug]: Signature redesign UI on mobile [Bug]: Reject and Confirm buttons on redesigned Signatures are not fully visible Feb 15, 2025
@metamaskbot metamaskbot added regression-develop Regression bug that was found on main branch, but not yet present in production and removed regression-RC-7.41.0 Regression bug that was found in release candidate (RC) for release 7.41.0 labels Feb 15, 2025
@sleepytanya sleepytanya added android Android specific issue regression-RC-7.41.0 Regression bug that was found in release candidate (RC) for release 7.41.0 and removed regression-develop Regression bug that was found on main branch, but not yet present in production labels Feb 15, 2025
@vpintorico vpintorico removed the release-blocker This bug is blocking the next release label Feb 17, 2025
@jpuri jpuri removed their assignment Feb 17, 2025
@jpuri
Copy link
Contributor

jpuri commented Feb 17, 2025

We need to adjust height of scrollable section above footer for android platform, for some reason my android setup is broken and I could not fix it.

@bschorchit bschorchit added the release-blocker This bug is blocking the next release label Feb 17, 2025
@vpintorico vpintorico removed the release-blocker This bug is blocking the next release label Feb 17, 2025
@OGPoyraz OGPoyraz removed their assignment Feb 18, 2025
@OGPoyraz OGPoyraz added the release-blocker This bug is blocking the next release label Feb 18, 2025
@sleepytanya sleepytanya changed the title [Bug]: Reject and Confirm buttons on redesigned Signatures are not fully visible [Bug]: Reject and Confirm buttons on redesigned Signatures are not fully visible when using larger font size Feb 18, 2025
@sleepytanya sleepytanya added release-blocker This bug is blocking the next release area-accessibility and removed android Android specific issue release-blocker This bug is blocking the next release labels Feb 18, 2025
@sleepytanya
Copy link
Contributor Author

Removing release-blocker as it is accessibility related issue.

@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Feb 19, 2025
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by severity Feb 19, 2025
@bschorchit bschorchit removed the release-blocker This bug is blocking the next release label Feb 19, 2025
@bschorchit bschorchit reopened this Feb 19, 2025
@github-project-automation github-project-automation bot moved this from Fixed to To be fixed in Bugs by team Feb 19, 2025
@bschorchit bschorchit removed the regression-RC-7.41.0 Regression bug that was found in release candidate (RC) for release 7.41.0 label Feb 19, 2025
github-merge-queue bot pushed a commit that referenced this issue Feb 20, 2025
## **Description**
Fix issue with footer buttons not visible in IOS with large fonts.

## **Related issues**

Fixes: #13516

## **Manual testing steps**

1. In IOS device enable large fonts
2. Go to test dapp and submit signature request
3. Check if footer buttons are clearly visible

## **Screenshots/Recordings**
LARGE FONTS:
<img width="394" alt="Screenshot 2025-02-20 at 3 31 43 PM"
src="https://github.com/user-attachments/assets/094f7998-885a-4247-80ce-8529ec8c7e1a"
/>

SMALL FONTS:
<img width="399" alt="Screenshot 2025-02-20 at 3 36 47 PM"
src="https://github.com/user-attachments/assets/bc2160e7-e6cd-4778-b463-aee55f16c984"
/>

## **Pre-merge author checklist**

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/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-mobile/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.
@sleepytanya
Copy link
Contributor Author

Closed by #13626

@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Feb 20, 2025
jpuri added a commit that referenced this issue Feb 25, 2025
Fix issue with footer buttons not visible in IOS with large fonts.

Fixes: #13516

1. In IOS device enable large fonts
2. Go to test dapp and submit signature request
3. Check if footer buttons are clearly visible

LARGE FONTS:
<img width="394" alt="Screenshot 2025-02-20 at 3 31 43 PM"
src="https://github.com/user-attachments/assets/094f7998-885a-4247-80ce-8529ec8c7e1a"
/>

SMALL FONTS:
<img width="399" alt="Screenshot 2025-02-20 at 3 36 47 PM"
src="https://github.com/user-attachments/assets/bc2160e7-e6cd-4778-b463-aee55f16c984"
/>

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] 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.
jpuri added a commit that referenced this issue Feb 25, 2025
Fix issue with footer buttons not visible in IOS with large fonts.

Fixes: #13516

1. In IOS device enable large fonts
2. Go to test dapp and submit signature request
3. Check if footer buttons are clearly visible

LARGE FONTS:
<img width="394" alt="Screenshot 2025-02-20 at 3 31 43 PM"
src="https://github.com/user-attachments/assets/094f7998-885a-4247-80ce-8529ec8c7e1a"
/>

SMALL FONTS:
<img width="399" alt="Screenshot 2025-02-20 at 3 36 47 PM"
src="https://github.com/user-attachments/assets/bc2160e7-e6cd-4778-b463-aee55f16c984"
/>

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] 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.
jpuri added a commit that referenced this issue Feb 25, 2025
Fix issue with footer buttons not visible in IOS with large fonts.

Fixes: #13516

1. In IOS device enable large fonts
2. Go to test dapp and submit signature request
3. Check if footer buttons are clearly visible

LARGE FONTS:
<img width="394" alt="Screenshot 2025-02-20 at 3 31 43 PM"
src="https://github.com/user-attachments/assets/094f7998-885a-4247-80ce-8529ec8c7e1a"
/>

SMALL FONTS:
<img width="399" alt="Screenshot 2025-02-20 at 3 36 47 PM"
src="https://github.com/user-attachments/assets/bc2160e7-e6cd-4778-b463-aee55f16c984"
/>

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] 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.
jpuri added a commit that referenced this issue Feb 25, 2025
## **Description**
Fix issue with footer buttons not visible in IOS with large fonts.

## **Related issues**

Ref: #13516

## **Manual testing steps**

1. In IOS device enable large fonts
2. Go to test dapp and submit signature request
3. Check if footer buttons are clearly visible

## **Screenshots/Recordings**
LARGE FONTS:
<img width="394" alt="Screenshot 2025-02-20 at 3 31 43 PM"
src="https://github.com/user-attachments/assets/094f7998-885a-4247-80ce-8529ec8c7e1a"
/>

SMALL FONTS:
<img width="399" alt="Screenshot 2025-02-20 at 3 36 47 PM"
src="https://github.com/user-attachments/assets/bc2160e7-e6cd-4778-b463-aee55f16c984"
/>

## **Pre-merge author checklist**

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/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-mobile/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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-accessibility Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking team-confirmations Push issues to confirmations team type-bug Something isn't working
Projects
Archived in project
Status: Fixed
6 participants