-
Notifications
You must be signed in to change notification settings - Fork 986
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
ensure chat headers are visible #4693
Conversation
chat-name]] | ||
[react/view {:style {:flex-direction :row}} | ||
(when public? | ||
[react/text "Public Chat"])] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rcullito please refer to any certain zeplin mock if any is implemented in PR |
@asemiankevich here is the most relevant link: https://app.zeplin.io/project/5a324ae5d60d197e7e3369cc/screen/5b16ef8daeac41933f425aa9 This PR does not completely match that design, but in particular I thought it would be convenient to add the text "public chat" while in the midst of fixing the "white panel issue" which this PR is meant to address. Let me know if any part of it is unclear! Thanks
|
1. Chat headers are cut when you are switching between them (chat with longer name should be started first)Steps:
Actual result:can see only first 5 chars of contact name in Chat header Expected result:Contact name is fully displayed Note: is reporducible when on 3 step you join to any public chat with name longer than on 5 step |
thanks for testing @churik. I will look into why the chat headers are cut as it relates to visibility issues brought up by #4249, which is what this PR aims to address. My aim was not to address all design feedback in this PR, but to open that up in a separate PR to come after these initial usability issues are fixed. I'll change the title of this PR to address that. Sorry for the confusion! |
explicitly add label for public chat remove unecessary margin at top of desktop chat view remove padding that was causing the white space which was blocking title try to be a bit more sane with which components in the chat header are flexing
@asemiankevich this latest commit should ensure that titles are always visible regardless of whether one is on initial page load or coming from a public chat to an individual one. There are still some issues of course plaguing the entire app around alignment, but hopefully this solves the visibility portion for now 🙏 Thanks for looking into it! |
@rcullito Also please request review from @cammellos or other mobile dev, it is required for now.
|
@rcullito
|
@churik thanks for the reminder on this! I'm aware that this is open/unresolved still. Let me know if I should indicate that in any way beyond being in the column: |
in recent talks it sounds like the fix for this is on the |
Fix for #4249 around visibility of chat headers.