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
As an end-user, if you connect to Sollet web and close the window, you're not capable of connecting again to Sollet web by selecting it again.
Reproduction steps
Go to /packages/example
Run yarn start
Select Sollet web with any of the UI options
Connect to the wallet
Close the window
Select Sollet web again
Expected behavior
As a user I would expect to be able to select Sollet web again and get prompted again. Even after closing the window.
Behavior found
The only way to get prompted again after closing the window is to select another wallet and then select Sollet web again.
Proposed solution
While working on #42 I noticed that if you close the window, an adapter disconnect event is fired leading to a "reset" of the state using initialState. When this happens, the state gets set to its initial value but the "selected wallet name" remains unchanged. I'm not sure if this is happening for the React package as well, but maybe all it takes is to call setName(null) on adapter disconnect.
The text was updated successfully, but these errors were encountered:
Overview
As an end-user, if you connect to Sollet web and close the window, you're not capable of connecting again to Sollet web by selecting it again.
Reproduction steps
/packages/example
yarn start
Expected behavior
As a user I would expect to be able to select Sollet web again and get prompted again. Even after closing the window.
Behavior found
The only way to get prompted again after closing the window is to select another wallet and then select Sollet web again.
Proposed solution
While working on #42 I noticed that if you close the window, an adapter disconnect event is fired leading to a "reset" of the state using
initialState
. When this happens, the state gets set to its initial value but the "selected wallet name" remains unchanged. I'm not sure if this is happening for the React package as well, but maybe all it takes is to callsetName(null)
on adapter disconnect.The text was updated successfully, but these errors were encountered: