-
Notifications
You must be signed in to change notification settings - Fork 81
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.
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
dApp - sd-6 - Same connected dApps appear on every account #15589
Comments
@glitchminer I missed these requirements and never planned to add filtering of dapps based on the account selected. Could you please clarify where are these coming from to see the complexity and if should we fix it now or leave it for later? In the meantime I will test if the problem is also happening with different profiles which we expect should not overlap. |
Hi @stefandunca, these are coming from manual test cases derived from some user stories. It will need confirmed with design now but Figma examples had the dapp button available on the individual account view only so there was an assumption that each account would display only dapps relevant to it. |
That will be god to understand; @xAlisher must know better the intention there. |
I agree with @glitchminer that most likely that was the initial intention. It's a different thing though whether it's high priority to have or the user can live with it as a global connected dapps list for M1 (cc @xAlisher)? How complex or time consuming do you think it will be to add @stefandunca? |
I didn't deal with handling of accounts switching and filtering recently and we don't have logic to hide/manage the button so I can't say. For me it is high risk, however maybe UI team have a different view on the matter. |
@stefandunca From what Alisher wrote on Discord:
I tend to agree with this. We also show unique connected dapps, right? If for instance two accounts are connected to the same dapp, would the user see two entries there or one? But even if we see two, the user wouldn't know which one to disconnect. IMHO this makes this issue a blocker. WDYT? |
Indeed I didn't considered and AFAIK we don't have anything related to the concept of important and unimportant wallet account in the wallet. It is the first time I hear about this persona characteristics I will consider it in the future.
Yes, we only show one and on disconnect it will disconnect all the sessions. I remember we had a similar discussed and considered a limitation given that we descoped the session management. I mean we discussed the fapt that user can connect from different browsers/systems with the same dApp and different accounts and it has no way to mange or visualize this in the current requirements (descoped designs).
It looks like. I will tackle this next then. Also there will be nice to have a clear description of this user story and acceptance criteria. For example should we show all connected dapps on all accounts selected (as it seems to me a way to be consistent)? |
I see the following requirements from @xAlisher in discord channel
|
do we have an "all accounts" page on desktop? |
Yup, it is the default view for wallet. I mean hiding the button on that page will hide the feature :) |
Then there we would show all active sessions |
@stefandunca mind assigning that to you if you are on this task? |
Bug Report
Description
Steps to reproduce
Connect to the same dApp from multiple wallet accounts
Expected behavior
Additional Information
The text was updated successfully, but these errors were encountered: