-
Notifications
You must be signed in to change notification settings - Fork 2.7k
MM-17477: Fix for group display name column expanding too large when … #3945
Conversation
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.
Given the time constraints, I'm going to approve this and the other PR, and will test after merged/cherry-picked.
@mkraft @lindalumitchell Is this urgent for v5.16 or can this be for v5.17? |
@mkraft is there a reason we aren't clipping the characters with an ellipses? |
@lindalumitchell This is separate; just a one-liner CSS change and not urgent. |
Thanks @mkraft, I'm fine with pushing the display issue to v5.17; was there a separate fix for the linking issue, with the Linked/Not Linked function failing if the name is too long? |
Ah cool, I thought that server PR was just display-related as well rather than function-related, thanks Amy. |
@lindalumitchell i couldnt figure out how to retest this to see if its been updated with my elipses suggestion or not.. |
@michaelgamble Per your ellipsis question... are you proposing adding an an ellipsis and only displaying less than 128 characters (which is the max) of the group display name? |
yeah thats my suggestion, having it extend and overlap other columns of data or break the table visually seem like a worse aesthetic I think there is a way to do it in CSS where the content is dynamically cut off based on the available width of the div that the content sits in with an elipses.. in my opinion that would be the best scenerio to solve this problem. |
@michaelgamble Is it currently extending and overlapping other columns with this fix? If so I wasn't aware of that. Also, how many characters would you have it display prior to en ellipsis? |
Last time i was able to look at a working test server with it, the overlapping is what i was seeing.. As far as the solution, it doesn't need to be a fixed character limit, you can just set the text-overflow:ellipsis; I think that will do what we want. |
@mkraft @michaelgamble is this one still in process for v5.17? Ideally we should aim to complete and review by EOD Thursday if possible for code complete. |
@michaelgamble Here's the screenshot with your requested changes: |
@lindalumitchell This is ready for QA now. |
Mattermost test server updated with git commit Access here: https://mattermost-webapp-pr-3945.test.mattermost.cloud |
@mkraft I'm testing this, and the display issue looks good, but I still am unable to click the link to link the group with the long name (it says Link Failed), and for some reason the LDAP sync is stuck on Pending as well. I tried the same LDAP instance on a v5.16 server and a master server, and both connected and synced without issue. So I'm not sure if there's an issue here that needs attention, or if somehow something expected is causing different behavior. Can you take a look with a test instance of LDAP that you have and see if anything looks wrong? |
Chatting with @mkraft and got the correct LDAP setup, and it is now connecting and syncing as expected, but linking the group with the long, truncated name is still failing. |
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.
Chatted more with @mkraft and it was a config issue; I replaced cn
with entryUUID
as the Group ID Attribute, and the long name still truncated as expected, and also I was able to link the group as expected. This looks good to me.
Test server destroyed |
@mkraft I think this is good to merge in and cherry-pick? |
…the name wraps.
Summary
Identified by QA during the case where a group's display name is > 128 characters in the linking phase: this change fixes the styling when the name wraps.
Ticket Link
https://mattermost.atlassian.net/browse/MM-17477