MetaMask Firefox Extension Outdated – Making Firefox Less Competitive and Buggy Compared to Chrome

Dear MetaMask Team,

I am writing to express my concern regarding the outdated version of the MetaMask extension available for Firefox. As of today, the latest version accessible in the Firefox Add-ons store is 12.06, which was released approximately three months ago. Meanwhile, the Chrome Web Store already offers version 12.10, which includes crucial bug fixes and improvements.

The 12.06 version on Firefox contains several unresolved bugs that significantly impact usability. However, since no newer version is available for Firefox, users are left without an option to update and benefit from the latest fixes. This creates an unfair discrepancy between browsers and leaves Firefox users stuck with outdated and potentially insecure software.

Key Concerns:

  1. Version Discrepancy: Chrome users have access to v12.10, while Firefox users are limited to v12.06.
  2. Buggy Experience: The 12.06 version contains known issues that have already been fixed in later versions for Chrome.
  3. Security & Feature Updates: Firefox users are missing out on critical security updates and new features.
  4. Impact on Firefox Competitiveness: By keeping the Firefox version outdated, Firefox is making itself a much less competitive browser for crypto users, forcing many to either switch to alternative wallets (such as Uniswap or Phantom) or migrate to Chrome just to use an up-to-date MetaMask extension.

Additional Concerns About Firefox Favoritism:

Given that other competing wallets continue to function properly while MetaMask remains outdated on Firefox, I am beginning to question whether Firefox is actively favoring other wallets over MetaMask on purpose. This is the only logical explanation for why MetaMask has been left behind while competing wallets remain unaffected. If there is another reason for this delay, then a clear explanation is needed from the Firefox team as to why MetaMask users are being neglected.

Request:

  • Please clarify why the Firefox extension is lagging behind in updates.
  • Provide an expected timeline for when the latest MetaMask version (12.10 or newer) will be available on Firefox.
  • If there are specific blockers preventing updates for Firefox, kindly communicate them to the community so we understand the delay.

If this issue is not addressed soon, it will inevitably push users away from both MetaMask and Firefox, benefiting competing wallets and browsers instead.

Looking forward to your response.

Best regards,

Adding to this, I have contacted metamask and they say the issue is on the Firefox side. They would gladly update the extension to the latest version if they could.

Metamask does not use Mozilla’s Discourse server for support. They appear to have their own community forum at https://community.metamask.io/. Maybe try re-posting over there?

It’s not a Metamask issue but a Firefox issue.

Based on this description it sounds like they’re encountering issues with review. Their best course is to reach out to addons.mozilla.org reviewers by either replying to the email set by Mozilla or adding a comment to the review history for the relevant version on the Developer Hub.

Ok, how can I personally reach out to them?

I don’t know. Metamask is developed by a separate company. I guess you could reach out however you did in your previous message.

I meant how can I reach out the reviewers. If I try to find their specific forum I just get back to this forum.

Maybe this is a better subforum to ask this? addons.mozilla.org - Mozilla Discourse

I archive the other thread to keep the conversation to a single thread. Reviewers do not frequent the discussion forums.

If you’re not a member of the MetaMask development team, the best you can do is try to relay to MetaMask how they can get in touch with Mozilla. Their first option is to reach out to Mozilla using one of the methods I previously mentioned. The second option would be for a member of that team to reach out on Mozilla’s #addon-reviewers Matrix channel. Third, they can post on this thread or message me directly and we can take the conversation offline.