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

Fixing scroll references for Advanced and Security settings #19771

Merged
merged 1 commit into from
Jul 11, 2023

Conversation

ryanml
Copy link
Contributor

@ryanml ryanml commented Jun 26, 2023

Related: #19479

Explanation

When anchoring to a settings search result that exists on the Advanced and Security tabs, many of the settings weren't scrolled to correctly, or at all. This is because there was an off by one error in the references ordering in the tab components when compared to the route positions in the settings constants. This PR fixes those off by ones, and in addition for Security constants, standardizes and fixes misspellings in the hash routes.

Before

(See video in referenced issue)

After

settings-fix.mov

Manual Testing Steps

  1. Navigate to the General Settings tab
  2. Using the settings search input, search for and anchor to various advanced and security settings. (Show balance and token price checker, Show hex data, Choose your network, etc)
  3. Ensure each setting clicked from in the suggestions is correctly scrolled to.

Pre-merge author checklist

  • I've clearly explained:
    • What problem this PR is solving
    • How this problem was solved
    • How reviewers can test my changes
  • Sufficient automated test coverage has been added

Pre-merge reviewer checklist

  • Manual testing (e.g. pull and build branch, run in browser, test code being changed)
  • PR is linked to the appropriate GitHub issue
  • IF this PR fixes a bug in the release milestone, add this PR to the release milestone

If further QA is required (e.g. new feature, complex testing steps, large refactor), add the Extension QA Board label.

In this case, a QA Engineer approval will be be required.

cc: @NiranjanaBinoy

@ryanml ryanml requested a review from a team as a code owner June 26, 2023 23:39
@github-actions
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@ryanml ryanml force-pushed the settings-ref-fixes branch from 868d511 to f271017 Compare June 26, 2023 23:55
@codecov
Copy link

codecov bot commented Jun 27, 2023

Codecov Report

Merging #19771 (f271017) into develop (04839a2) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop   #19771      +/-   ##
===========================================
- Coverage    69.85%   69.85%   -0.01%     
===========================================
  Files          980      980              
  Lines        36909    36909              
  Branches      9908     9908              
===========================================
- Hits         25782    25780       -2     
- Misses       11127    11129       +2     
Impacted Files Coverage Δ
ui/helpers/constants/settings.js 33.78% <ø> (ø)
...es/settings/advanced-tab/advanced-tab.component.js 59.76% <ø> (ø)
...es/settings/security-tab/security-tab.component.js 77.42% <ø> (ø)

... and 2 files with indirect coverage changes

@NiranjanaBinoy NiranjanaBinoy mentioned this pull request Jul 10, 2023
8 tasks
Copy link
Contributor

@NiranjanaBinoy NiranjanaBinoy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me.

Good to see you @ryanml

Copy link
Member

@NidhiKJha NidhiKJha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks, @ryanml

@NidhiKJha NidhiKJha merged commit 8e55e95 into MetaMask:develop Jul 11, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jul 11, 2023
@Gudahtt Gudahtt added the release-10.35.0 Issue or pull request that will be included in release 10.35.0 label Sep 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-10.35.0 Issue or pull request that will be included in release 10.35.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants