Skip to content
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

Threads design implementation review #19669

Closed
49 of 53 tasks
janogarcia opened this issue Nov 9, 2021 · 3 comments
Closed
49 of 53 tasks

Threads design implementation review #19669

janogarcia opened this issue Nov 9, 2021 · 3 comments
Assignees

Comments

@janogarcia
Copy link

janogarcia commented Nov 9, 2021

Thread panel button


  • When viewing a thread if you click on the threads panel icon on the room header the thread panel will navigate back to the thread list view. Clicking on the thread panel icon should always toggle on/off the thread panel, not navigate back.



Thread list

Thread detail

  • Empty state: Fix the broken layout for the case where the root message has been deleted.
  • The overflow/3-dot icon mask CSS property is set to 18px, which effectively makes the icon to render at 18px, instead of 24px.
  • There should be a 12px gap to both sides of content. https://cloudup.com/cH8LKHcO3RK
  • The timestamp should be displayed below the avatar as in the room timeline, instead of taking up space on the right area. https://cloudup.com/cH8LKHcO3RK

Thread panel

  • The top right corner in the main container (white) should be round, not square.
  • Bottom padding should be 8px instead of 4px.
  • Right padding should be 8px.
  • The back button should read “All threads”, instead of “Back”.
 Figma
  • Fix header right padding.
  • The panel header should be always the same height, it currently differs depending if you're on the thread list or thread detail view.
  • Header overflow button icon.
    • What is the issue here?
  • persist the hover state of the message action bar for TileShape.ThreadPanel
  • The persisted hover state when the Thread options menu is revealed is not being applied to the top of the thread tile
  • Display e2ee shield under the user avatar, at the moment it's overlays the body
  • The thread header should be vertically centered. https://cloudup.com/cINen7xTsZn
  • Use the same background color for the pointing triangle in the filter popover in dark mode #20872

Thread summary

  • Show right chevron on hover. Figma
  • Thread icon should be 18x18px
  • The thread summary container height should be 40px (as a result of adding 8px top and bottom padding to the 24px avatar)
  • Separate the thread summary by an additional 8px distance from the reactions container (e.g. using the adjacent sibling combinator .mx_ReactionsRow + .mx_ThreadInfo { margin-top: 8px; })
  • Apply the same line height of the reply excerpt to the reply count label, for better optical vertical alignment.
  • Spacing between the reply count and the avatar of the latest reply should be 12px, instead of 8px.
  • Implement the expected fluid width behavior. For example, by setting .mx_ThreadInfo { display: inline-flex; } rather than display: flex;.

Other

  • Don’t show a “Show threads” action in the Room Info panel.
  • The tooltip in the room timeline contextual actions should read “Reply in thread”, instead of just “Thread”
@germain-gg
Copy link
Contributor

The thread tiles should be ordered from latest reply date, newest on the top.

The client can manage that state once Element is running. However for the initial state, Synapse will need to return a sorted list of threads.

@clokep is it possible to achieve that? My guess is no, because that means that the pagination token would not be idempotent anymore

@clokep
Copy link

clokep commented Nov 9, 2021

The thread tiles should be ordered from latest reply date, newest on the top.

The client can manage that state once Element is running. However for the initial state, Synapse will need to return a sorted list of threads.

@clokep is it possible to achieve that? My guess is no, because that means that the pagination token would not be idempotent anymore

I believe for this you're planning to use the /messages endpoint which supports ordering.

@germain-gg germain-gg removed their assignment Feb 18, 2022
@novocaine novocaine changed the title Design implementation review Threads design implementation review Mar 17, 2022
@janogarcia
Copy link
Author

@gsouquet Closing this one in favor of #21502 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants