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
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
I've noticed that Dappeteer currently suggests using an older version of Metamask, which can cause issues with compatibility. This happens because Metamask frequently updates its features and security measures. As a result, users of Dappeteer who rely on external webdriver-based apps, like myself, face difficulties due to recent security improvements in Metamask that intentionally limit the use of certain functions (restricting the global object of the application). While these security enhancements are crucial, they create challenges for Dappeteer users.
Describe the solution you'd like
I kindly request support for the latest secure versions of Metamask in Dappeteer. It would be highly beneficial if Dappeteer could be updated to seamlessly work with the most recent Metamask releases. This way, users can fully utilize the latest features and security improvements without facing compatibility issues.
Additional context
I appreciate the security-focused approach that Metamask has taken. Could you please let me know if there are any plans or a roadmap for implementing this support in Dappeteer? I understand that it might take some time and resources, but having information about your intentions would be very helpful. Thank you.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I've noticed that Dappeteer currently suggests using an older version of Metamask, which can cause issues with compatibility. This happens because Metamask frequently updates its features and security measures. As a result, users of Dappeteer who rely on external webdriver-based apps, like myself, face difficulties due to recent security improvements in Metamask that intentionally limit the use of certain functions (restricting the global object of the application). While these security enhancements are crucial, they create challenges for Dappeteer users.
Describe the solution you'd like
I kindly request support for the latest secure versions of Metamask in Dappeteer. It would be highly beneficial if Dappeteer could be updated to seamlessly work with the most recent Metamask releases. This way, users can fully utilize the latest features and security improvements without facing compatibility issues.
Additional context
I appreciate the security-focused approach that Metamask has taken. Could you please let me know if there are any plans or a roadmap for implementing this support in Dappeteer? I understand that it might take some time and resources, but having information about your intentions would be very helpful. Thank you.
The text was updated successfully, but these errors were encountered: