This PR solves the issue https://github.com/poanetwork/poa-dapps-validators/issues/85 and makes some refactoring of code. MetaMask v4.14.0 (and above) will display the next confirmation message when a user opens DApp for the first time after November 2nd, 2018:
If the user clicks on Approve, the DApp will load and continue working. Otherwise (in the case of Reject), DApp will show the next alert and stop execution:
If the user clicks on Approve, MetaMask will cache user's choice and won't ask the user again next time until he/ she clears approval data in MetaMask's settings.
(Mandatory) Description
This PR solves the issue https://github.com/poanetwork/poa-dapps-validators/issues/85 and makes some refactoring of code. MetaMask v4.14.0 (and above) will display the next confirmation message when a user opens DApp for the first time after
November 2nd, 2018:If the user clicks on
Approve, the DApp will load and continue working. Otherwise (in the case ofReject), DApp will show the next alert and stop execution:If the user clicks on
Approve, MetaMask will cache user's choice and won't ask the user again next time until he/ she clears approval data in MetaMask's settings.The custom build of MetaMask for testing can be downloaded here: https://github.com/MetaMask/metamask-extension/pull/4703#issuecomment-427062852.
These changes are backward compatible, so the new code will work fine with old DApp browsers that don't support
ethereum.enable()feature yet.(Mandatory) What is it: (Fix), (Feature), or (Refactor) (Fix, Refactor)