MetaMask / MetaMask/metamask-extension
deeplink: if lock screen is refreshed during deep link flow it should resume the flow, not unlock to the home page
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
See https://github.com/MetaMask/metamask-extension/pull/33639#issuecomment-2982034787
### Scenario
_No response_
### 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
_No response_
Contributor guide
Research direction
Start by reading the discussion linked from PR #33639, especially the referenced issue comment, to reconstruct the deep-link and lock-screen flow. Trace where a refreshed lock screen resumes or exits that flow; done means a refresh returns the user to the active deep-link flow rather than unlocking to the home page, with behavior covered by the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100