-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Redesign: Remaining bits after both user and room settings are implemented #8207
Comments
@lampholder feedback incorporated into the main post. On the specific items:
See #8249
I've opened this as #8268 (as per our discussion)
Both of these I've put under "fix the device table design" (it's squishy, and that causes a lot of problems) |
Having thought about the device list UI a little over the past few days, I've uploaded my most recent sketch of a cards-based device list #8319 |
I've also spotted another UX issue - when the flow returns a user to settings after they've diverted elsewhere (via the E2E beta warning modal when enabling encryption in a room, or via the key backup UX when configuring key backup on an account) the user lands on the first page of settings, not the page they were on before. How easy is this to fix? It's certainly jarring landing on an unexpected page, but I can also see it might be tricky to address quickly. |
And one more issue - I don't think it's possible to delete an avatar any more. I'd suggest putting the delete X we have in other places as close as possible to the avatar square (with the 'Remove Avatar' tooltip we have in the /app build of riot) |
And another one - can we enable Esc closing the settings modal? |
I'd rather not fix our dialog system this week, and would classify the problem as Very Hard to fix.
Already planned by proxy for Part 2 fixes. |
We should avoid an X at all costs - it confuses everyone. I'd like to get Nad in on this decision. |
Removing avatars is being tracked outside of this: #8456 |
I'm considering this done enough to take it off my top priority list. The remaining work I've shuffled into "p4" (which is relative to the items on this issue). I've also made a note to come back to it in a few months if we haven't managed to make our way around to it. |
I think most of this is now just bugs or things we fixed by changing the design (accidentally and sometimes on purpose). Closing in favour of the already-open issues. We also don't really use epics like this anymore, so this is potentially lost to time 😬 |
Part 0 (already fixed prior to grouping):
Part 1 (PR: matrix-org/matrix-react-sdk#2526):
Part 2 (PR: matrix-org/matrix-react-sdk#2549):
Part 3 (PR: matrix-org/matrix-react-sdk#2553):
Part 4 (PR: matrix-org/matrix-react-sdk#2554):
Priority 2 problems ("would be really nice if..." items):
EditableItemList
should be usingField
, not whatever it currently is (aliases, related groups)DragDropContext
over the flair settings - PR: Maintenance: Clean up some stuff around settings matrix-org/matrix-react-sdk#2685Priority 3 problems ("if someone gets bored and has time..." items):
Priority 4 problems ("Eventually, we will fix..." items):
The text was updated successfully, but these errors were encountered: