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

Signatures redesign - confirm button is disabled even if full content is visible and no scroll arrow is shown #24485

Closed
9 tasks
bschorchit opened this issue May 10, 2024 · 0 comments · Fixed by #24489 or #24527
Assignees
Labels
release-11.18.0 Issue or pull request that will be included in release 11.18.0 release-blocker This bug is blocking the next release team-confirmations Push issues to confirmations team

Comments

@bschorchit
Copy link

What is this about?

Confirm button should be enabled when full content is visible and the scroll to bottom arrow is not present.

Scenario

  • Go to opensea.io
  • Connect your wallet
  • Get prompt the personal sign request to sign in

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

Screen.Recording.2024-05-10.at.12.30.06.mov
@bschorchit bschorchit added the team-confirmations Push issues to confirmations team label May 10, 2024
@digiwand digiwand self-assigned this May 14, 2024
digiwand added a commit that referenced this issue May 14, 2024
…Bottom button with 16px or less scroll buffer (#24489)

## **Description**

- Removes 16px buffer
- Allow optional scroll buffer in useScrollRequired hook

## **Related issues**

Fixes: #24485

## **Manual testing steps**

1. Create sign request from OpenSea login
2. Observe scroll behavior 

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**


https://github.com/MetaMask/metamask-extension/assets/20778143/1b436528-b285-41c0-a365-98ce2aed7eec

### **After**


https://github.com/MetaMask/metamask-extension/assets/20778143/4a42022a-1473-4f9c-b3a5-459510f221c2

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.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.
@metamaskbot metamaskbot added the release-11.18.0 Issue or pull request that will be included in release 11.18.0 label May 14, 2024
@bschorchit bschorchit added the release-blocker This bug is blocking the next release label May 14, 2024
digiwand added a commit that referenced this issue May 14, 2024
…Bottom button with 16px or less scroll buffer (#24489)

## **Description**

- Removes 16px buffer
- Allow optional scroll buffer in useScrollRequired hook

## **Related issues**

Fixes: #24485

## **Manual testing steps**

1. Create sign request from OpenSea login
2. Observe scroll behavior 

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**


https://github.com/MetaMask/metamask-extension/assets/20778143/1b436528-b285-41c0-a365-98ce2aed7eec

### **After**


https://github.com/MetaMask/metamask-extension/assets/20778143/4a42022a-1473-4f9c-b3a5-459510f221c2

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.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.
danjm pushed a commit that referenced this issue May 20, 2024
…d "Confirm" button with 16px or less scroll buffer (#24527)

<!--
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**

Cherry-pick
[0e775fd](0e775fd)
(#24489) into
v11.17.0

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24527?quickstart=1)

## **Related issues**

Fixes: #24485

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.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
release-11.18.0 Issue or pull request that will be included in release 11.18.0 release-blocker This bug is blocking the next release team-confirmations Push issues to confirmations team
Projects
None yet
3 participants