Used KTextTruncator in ReviewSelectionsPage to avoid text collision #4870
Conversation
There was a problem hiding this comment.
I have tested the changes locally and the text collision does not exist now. Thanks @shruti862!
There was a problem hiding this comment.
Hi @shruti862, thanks! Even though this resolved the text collision, there is a regression. Previously, items in the list would be formatted as links, and clicking the item would open a resource. This functionality is now lost. #4086 needs to be fixed in a way that doesn't break this.
I believe that in #4591, @lokesh-sagi125 works on some other places that need KTextTruncator and is currently dealing with some things related to ActionLink and KTextTruncator that could perhaps be relevant here as well. @lokesh-sagi125 would you coordinate with @shruti862 and mention more details?
|
yes @MisRob even though my implementation is still acting like a link , the underline part is not inherited. will try researching other possible solutions:) |
Summary
Added KTextTruncator in ReviewSelectionsPage to avoid resource title collision with Channel name.
After Change:
…
References
Fixes issue #4086
…
Reviewer guidance
…