search

kohkaijie / pe

0 stars 0 forks source link

Truncated UI for very long names #5

Open kohkaijie opened 11 months ago

kohkaijie commented 11 months ago

Steps to reproduce: edit 2 n/Hubert Blaine Wolfeschlegelsteinhausenbergerdorff Wolfeschlegelsteinhausenbergerdorff Sr

While such long names are extremely rare, one cannot discount the possibility that it may happen as such long names do exist and the UI should be able to handle such inputs

image.png

nus-se-bot commented 11 months ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Long inputs are cut off

Long names can get cut off when the window is small. Though this is a cosmetic issue, it can still affect readability.

Screenshot 2023-11-17 at 5.02.25 PM.png

[original: nus-cs2103-AY2324S1/pe-interim#5199] [original labels: type.FunctionalityBug severity.VeryLow]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Hello! Thank you for the bug reject. However, we regret to inform you that we will be rejecting this bug. It does not classify under FunctionalityBug as we have already stated in our UG that Texts that exceed the UI will be truncated and not wrapped.

Screenshot 2023-11-20 at 2.46.27 AM.png

As stated below from the course website, the behaviour does not differ from the user guide and hence is not a functionality bug.

Screenshot 2023-11-20 at 2.45.31 AM.png

Thank you!

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** My apologies, the bug type that I chose was wrong and it should be a FeatureFlaw instead. However, I disagree that this is not a bug even though it is stated in the UG that long names will be truncated. In a real world scenario, the app should be able to support long names and failure to do so may be a hindrance to users, even though it only occurs in rare cases. Since this behaviour was stated in the UG, I agree that it should not be a functionality bug but it should be a feature flaw due to the app's limitations as it provides clear inconvenience to users with long names.