MetaMask / MetaMask/metamask-extension

MV3: Support dapp legacy provider

Open
#15,988 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

MV3 team-extension-platform
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### Describe the bug

This support should piggyback off the support we have for dapp pages. It might already be supported with the dapp work found in the related epics.

### Steps to reproduce

### Error messages or log output

_No response_

### Version

10.19.x

### Build type

_No response_

### Browser

Chrome

### Operating system

MacOS

### Hardware wallet

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by reviewing the related dapp-page epics and the MV3 provider integration, then reproduce the legacy-provider behavior in Chrome. Done means confirming whether existing dapp support covers the legacy provider or identifying the missing support and adding focused coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.