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]: Whenever an NFT is sent through the Send flow, a console message appears: TypeError#24:Cannot read properties of undefined (reading 'scrollTo'). #29226

Closed
sleepytanya opened this issue Dec 16, 2024 · 1 comment · Fixed by #29386
Assignees
Labels
needs-triage regression-RC-12.10.0 Regression bug that was found in release candidate (RC) for release 12.10.0 release-12.11.0 Issue or pull request that will be included in release 12.11.0 Sev3-low Low severity; minimal to no impact upon users team-bridge type-bug

Comments

@sleepytanya
Copy link
Contributor

Describe the bug

Whenever an NFT is sent through the Send flow, a console message appears: TypeError#24:Cannot read properties of undefined (reading 'scrollTo').

Expected behavior

Screenshots/Recordings

sendflowNft.mov
Image

Steps to reproduce

  1. Send an NFT from the Send flow

Error messages or log output

Detection stage

During release testing

Version

v12.10.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

@sleepytanya sleepytanya added regression-RC-12.10.0 Regression bug that was found in release candidate (RC) for release 12.10.0 Sev3-low Low severity; minimal to no impact upon users team-assets type-bug labels Dec 16, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Dec 16, 2024
@sleepytanya sleepytanya added the team-confirmations Push issues to confirmations team label Dec 16, 2024
@vinistevam vinistevam added team-bridge and removed team-assets team-confirmations Push issues to confirmations team labels Dec 16, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Dec 19, 2024
@DDDDDanica DDDDDanica self-assigned this Dec 20, 2024
@DDDDDanica
Copy link
Contributor

Fixed: #29386

github-merge-queue bot pushed a commit that referenced this issue Dec 20, 2024
<!--
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**
When switching to another non-ERC721 NFT in send flow, it is possible
that the input is undefined when rendered. As we didn't need to use
`scrollTo` for this input (introduced
[here](https://github.com/MetaMask/metamask-extension/pull/25307/files#diff-5b53d7ec060521a384c4dff7468398b01e302ac17511f243b79a5dd1d1cb69d3))
, putting a conditional running is sufficient.

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

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

## **Related issues**

Fixes: #29226

## **Manual testing steps**

1. Go to NFT
2. Pick a non ERC721 NFT to send
3. Should not see errors in console when in the sending form

## **Screenshots/Recordings**

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

### **Before**


https://github.com/user-attachments/assets/98268028-fcb1-419e-8638-bb3cbc482b3c


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

### **After**


https://github.com/user-attachments/assets/830f40c3-0601-4eab-971f-eb69f253c084

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

## **Pre-merge author checklist**

- [ ] 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).
- [ ] 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/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.
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by severity Dec 20, 2024
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by team Dec 20, 2024
@metamaskbot metamaskbot added the release-12.11.0 Issue or pull request that will be included in release 12.11.0 label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage regression-RC-12.10.0 Regression bug that was found in release candidate (RC) for release 12.10.0 release-12.11.0 Issue or pull request that will be included in release 12.11.0 Sev3-low Low severity; minimal to no impact upon users team-bridge type-bug
Projects
Archived in project
Status: Fixed
Development

Successfully merging a pull request may close this issue.

4 participants