mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-29 07:16:36 +01:00
943453cfb2
* Simplify MV3 initialization The MV3 initialization logic was complicated and introduced race difficult-to-reproduce race conditions when dapps connect during initialization. It seems that problems were encountered after the UI tried to connect before the background was initialized. To address this, the initialization step was _delayed_ until after the first connection. That first connection was then passed into the initialization function, and setup properly after initialization had begun. However, this special treatment is only given for the first connection. Subsequent connections that still occur during initialization would fail. This also results in the initialization being needlessly delayed, which is concerning given that our main performance goal is to speed it up. * Setup connect listeners before controller initialization * Add comments * Add comment explaining isInitialized step |
||
---|---|---|
.. | ||
account-import-strategies | ||
constants | ||
controllers | ||
flask | ||
lib | ||
migrations | ||
platforms | ||
app-init.js | ||
background.js | ||
contentscript.js | ||
detect-multiple-instances.js | ||
detect-multiple-instances.test.js | ||
disable-console.js | ||
first-time-state.js | ||
init-globals.js | ||
inpage.js | ||
lockdown-more.js | ||
lockdown-run.js | ||
metamask-controller.actions.test.js | ||
metamask-controller.js | ||
metamask-controller.test.js | ||
sentry-install.js | ||
ui.js | ||
use-snow.js |