Page MenuHomePhabricator

Fixed incorret display for long thread names on web.
AbandonedPublic

Authored by kuba on Jan 26 2023, 2:56 AM.
Tags
None
Referenced Files
F3537753: D6393.id21348.diff
Wed, Dec 25, 10:12 PM
F3537658: D6393.id.diff
Wed, Dec 25, 10:10 PM
F3537546: D6393.diff
Wed, Dec 25, 9:58 PM
Unknown Object (File)
Tue, Dec 17, 2:51 AM
Unknown Object (File)
Nov 24 2024, 5:57 PM
Unknown Object (File)
Nov 24 2024, 3:55 PM
Unknown Object (File)
Nov 19 2024, 10:01 AM
Unknown Object (File)
Nov 19 2024, 9:59 AM

Details

Summary

Fixing: https://linear.app/comm/issue/ENG-2610/top-bar-on-web-displays-incorrectly-for-long-names
I needed to make broad changes to top bar, as it was not styled correctly, so fix was really using flexbox correctly and then make overflow appear as ellipsis.

Test Plan

Screen shots:

Screenshot 2023-01-26 at 11.54.32.png (273×590 px, 24 KB)

Screenshot 2023-01-26 at 11.54.27.png (145×1 px, 20 KB)

Screenshot 2023-01-26 at 11.54.38.png (162×1 px, 21 KB)

Diff Detail

Repository
rCOMM Comm
Branch
fix/long-names
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

web/chat/chat-thread-ancestors.css
6

we set shrink to 0.75 as we want threads container shrink less, so it occupy larger part of a screen than thread name itself. I found that value the best, and I couldn't find strict specification in Figma

8–15

now ancestor name is "artistic" styles only, and not layout related. We handle layout with seperate css classes for each element: .ancestorKeyserver, .middle, .currentThreadName

45

I used those on elements that shouldn't grow nor shrink like menu dots on the right, color thread box or svg arrow separators

49–51

Used for creating ellipsis

54

we need this in flex items that we want to overflow using ellipsis: https://bugzilla.mozilla.org/show_bug.cgi?id=1086218#c4
Related SO issue: https://stackoverflow.com/questions/26465745/ellipsis-in-flexbox-container

Note that this diff is not tied to monthly goals, so reviewers (and author) please treat it as low-pri

It sounds like @inka is going to take this on since she's restyling the "top bar" anyways

This revision should be closed since this bug was fixed in D6851 and D6845

@inka fixed this in another diff.