nus-pe-script
commented
2 years ago Team's Response
Decision
Rejected, due to action by deliberate sabotage
Reason for Rejection
We note that the tester had to type around or even more than 200 characters before the overflow starts to happen. This is not a meaningful name and few persons have names spanning 200 characters.
Therefore, this is an extreme user behaviour and is an act of deliberate sabotage to find bugs.
The issue does not cause much harm to the user and the app is still usable, so we don't agree that this is a bug. There is also insufficient grounds to show that this is an issue worth Low severity as it is a cosmetic issue, not one related to the behaviour of a function.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Currently, there doesn't seem to be any given limit on character count in a name, but if you input a name that is too long, it gets cut off and there doesn't seem to be a way to view the full name even in the bottom box with the expanded view
I put in a random keysmash that was pretty long but there might be someone out there with a name that long I guess - should probably either state a hard character limit in the UG or find a way to allow scroll to see the full name in the inspect box