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

chore(runway): cherry-pick feat: add favorites to browser menu #12078

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

runway-github[bot]
Copy link
Contributor

@runway-github runway-github bot commented Oct 29, 2024

Description

We're adding in a "Go to Favorites" option into the browser menu so
users can navigate to https://home.metamask.io, allowing them to access
their previous favorites pages. After switching to the Portfolio dapps
for a user's homepage, we received a decent amount of user feedback
wanting this feature back in.

Related issues

Fixes:

Manual testing steps

  1. Open the in-app browser
  2. Navigate to any website that's not https://home.metamask.io
  3. Open the browser menu by tapping on the "more" icon
  4. See the new "Go to Favorites" option, tap that.
  5. Confirm that the user is taken to https://home.metamask.io

Screenshots/Recordings

Before

IMG_8936

After

Screenshot 2024-10-28 at 11 13 04 AM

Actual

favorite.mov

Pre-merge author checklist

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.

Signed-off-by: Kai Huang kai.huang@consensys.net
Co-authored-by: Cal-L cleun007@gmail.com
Co-authored-by: legobeat 109787230+legobeat@users.noreply.github.com
Co-authored-by: Cal Leung cal.leung@consensys.net 36d2535

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

We're adding in a "Go to Favorites" option into the browser menu so
users can navigate to https://home.metamask.io, allowing them to access
their previous favorites pages. After switching to the Portfolio dapps
for a user's homepage, we received a decent amount of user feedback
wanting this feature back in.

## **Related issues**

Fixes:

## **Manual testing steps**

1. Open the in-app browser
2. Navigate to any website that's not https://home.metamask.io
3. Open the browser menu by tapping on the "more" icon
4. See the new "Go to Favorites" option, tap that.
5. Confirm that the user is taken to https://home.metamask.io

## **Screenshots/Recordings**

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

### **Before**


![IMG_8936](https://github.com/user-attachments/assets/36f65f0c-7929-4058-98ba-5800aec70be5)

### **After**

![Screenshot 2024-10-28 at 11 13
04 AM](https://github.com/user-attachments/assets/68a2898e-2a72-43ee-8572-155a7b5a2028)

Actual


https://github.com/user-attachments/assets/e6aabfd6-3746-4075-ad47-b8140afbc3fd



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

## **Pre-merge author checklist**

- [ ] 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).
- [ ] 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-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.

---------

Signed-off-by: Kai Huang <kai.huang@consensys.net>
Co-authored-by: Cal-L <cleun007@gmail.com>
Co-authored-by: legobeat <109787230+legobeat@users.noreply.github.com>
Co-authored-by: Cal Leung <cal.leung@consensys.net>
@runway-github runway-github bot requested a review from a team as a code owner October 29, 2024 16:05
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.

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 60%)

See analysis details on SonarCloud

@sethkfman sethkfman added No QA Needed Apply this label when your PR does not need any QA effort. skip-sonar-cloud Only used for bypassing sonar cloud when failures are not relevant to the changes. labels Oct 29, 2024
Copy link
Contributor

@sethkfman sethkfman left a comment

Choose a reason for hiding this comment

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

LGTM

@sethkfman sethkfman merged commit c8174c7 into release/7.34.0 Oct 29, 2024
38 of 40 checks passed
@sethkfman sethkfman deleted the runway-cherry-pick-7.34.0-1730217906 branch October 29, 2024 17:41
@github-actions github-actions bot locked and limited conversation to collaborators Oct 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
No QA Needed Apply this label when your PR does not need any QA effort. skip-sonar-cloud Only used for bypassing sonar cloud when failures are not relevant to the changes. team-runway-bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants