New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't expect Web3 to be provided, but use the postMessage API #527

Open

Qkyrie opened this issue Aug 10, 2018 · 0 comments

Labels

Bug Community Enhancement

Contributor

Qkyrie commented Aug 10, 2018

Expected behaviour

use the postMessage API instead of expecting web3 to be injected

Actual behaviour

expecting Web3 to be injected

see:

https://medium.com/metamask/https-medium-com-metamask-breaking-change-injecting-web3-7722797916a8

Qkyrie added Bug Enhancement Community labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment