trash-bin99 / pe

0 stars 0 forks source link

Long addresses not able to be fully viewed by the user #5

Open trash-bin99 opened 2 years ago

trash-bin99 commented 2 years ago

image.png

To reproduce this: Type in the command

touch -n verylongname -p 98765432 -e johnd@example.com -a John street, block123, #01-01, fillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfillerfiller

Expected: Address should be fully viewable even though it is very long

Actual: Address is truncated by ellipses

Although this was mentioned in the user guide, it still feels like a feature flaw as a long address is not viewable by the user, and instead truncated. The information typed in by the user should be fully viewable by them, otherwise it is a waste of their time typing it in. Other measures could have been taken to mitigate this, such as by text wrapping the address.

nus-pe-bot commented 2 years ago

Team's Response

No details provided by team.

The 'Original' Bug

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

Full address cannot be viewed if it is too long

Screenshot 2021-11-12 at 4.57.00 PM.png

This limitation is stated in User Guide, but it will still affect the user should they want to save a contact with long address but does not have sufficient screen real estate


[original: nus-cs2103-AY2122S1/pe-interim#3557] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

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

Potential case of deliberate sabotage.

image.png

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]

Reason for disagreement: [replace this with your explanation]