Mark Stacey b58c0d7810 Skip state update upon failure (#8432) ... Many of the "message manager" background methods return a full copy of the background state in their response; presumably to save us from making a full round-trip to update the UI `metamask` state after it changes. However, the action creators responsible for calling these methods were calling `updateMetamaskState` even when the background method failed. In effect, they were setting the UI `metamask` state to `undefined`. They have been updated to only set the UI `metamask` state if the background method succeeded.		2020-04-27 20:32:15 -03:00
..
app	Skip state update upon failure (#8432)	2020-04-27 20:32:15 -03:00
lib	Prevent accidental use of globals (#8340)	2020-04-15 14:23:27 -03:00
index.js	LoginPerSite: Support multiple accounts without automatic switching (#8079)	2020-03-06 13:34:56 -08:00