Open WuJinhan1 opened 1 week ago
Thank you for this point. During our design we had to deliberate between restricting name length, wrapping the text or leaving as it is in the picture. However, restricting name length felt like an overzealous input validation case where there was not much value aside from aestheticism, and wrapping the text will suffer the same issue if a user sabotages with even longer names anyway. We believe leaving it as it is (overflowing) is the best decision as, when we look from a user perspective:
Team chose [response.Rejected
]
Reason for disagreement: Yes, although that may be true, you have to consider the fact that this was on full screen, and the number of characters shown would only decrease with a smaller window. Also, I have tested the other fields and it seems that email has the same issue of overflowing, and when clicked on to open the personal detail view, even more characters overflow, reducing visibility. Therefore, although names of such length may be rare, emails exceeding the limit are more likely. While I have put the severity of the issue as low, it should not be rejected.
When a person with a really long name is added, you are not able to see the rest of his/her name