You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beginning even before #178 was opened, the Metamask extension has been broken in Mullvad Browser. With every update since, I've diligently rechecked its status and nothing has changed. The problem hasn't even been acknowledged aside from a generic label addition in March.
Also can't use any extension so far that requires a login (which includes NordVPN). I have a very limited understanding of browser security, so from a laymans point of view, this seems like "ultra secure", but I also want to use my computer...
So for me at this point, it seems like Mullvad can't be a "daily" driver for the regular user and has no place being set as the default browser like many users are recommending (imagine the onslaught of issue reports by regular users who just think their extensions are broken!! - like me 😇). It's more of a security anxious user who's happy with forgoing a multitude extensions.
So, given I have a choice between vpn or secure Firefox mod. I will just go down the semi-hardened Firefox route, so I can have some better privacy while still being able to use extensions.
Beginning even before #178 was opened, the Metamask extension has been broken in Mullvad Browser. With every update since, I've diligently rechecked its status and nothing has changed. The problem hasn't even been acknowledged aside from a generic label addition in March.
As noted in other comments there, it's not a Firefox issue because the extension works in other forks. The problem is also not isolated to Metamask as https://enkrypt.com's extension essentially has a seizure trying to use it with Mullvad Browser. It's hard for this to ever be a default browser option if extensions remain broken for this long: https://mullvad.net/en/blog/mullvad-browser-135-released-with-letterboxing-improvements-and-new-installation-options
The text was updated successfully, but these errors were encountered: