search

Zer0Legion / pe

0 stars 0 forks source link

UI cut off with no other way to find out the hidden information #7

Open Zer0Legion opened 7 months ago

Zer0Legion commented 7 months ago

Expected: The app enables user to see too long names, or at least restricts the length if the app is unable to handle it.

Actual: Although the DG states a subset of this issue in planned enhancements, I am at the maximum possible window size on a 24 inch monitor and am still unable to view the full name of Pablo Picasso.

Vague and sweeping planned enhancement in DG:

My window size is the maximum possible on a 24 inch monitor. Perhaps the evaluator could test this as well.

image.png

My screen size is not reduced at all: image.png

Hence I feel that this is a valid bug report.

Contacts bar:

image.png

Contact card:

image.png

soc-se-bot commented 7 months ago

Team's Response

Thank you for the bug report. See the clarification by Prof on UI text truncation below:

image.png

I sympathize your trouble in viewing Pablo Picasso's full name of 131 characters, however, our planned enhancement in the DG does mention that we intend to handle longer inputs such as this. Extreme inputs such as these are considered "nice to have features". This is why we have decided this to be NotInScope.

In addition to this, see this section on the PE instructions:

image.png

At least the first 7 of Picasso's 25 names can be viewed on my smaller screen, therefore we do not find this to hinder the user significantly. This is why we have decided to downgrade the severity to VeryLow as this seems to be a cosmetic issue.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The team merely has repeated what I have observed in the planned enhancements section. It does not address the issue that I find the writeup to be over-generalizing and sweeping:

To reiterate my concern:

The planned enhancements section has covered:

  1. Long text may not appear in smaller windows, but can be seen after enlarging the window.
  2. Issues with UI cutoff when screen size is reduced.

My concern is that the UI still cuts off even when I:

  1. have my window to the maximum I can do;
  2. did not do any reduction of screen size.

In the same screenshot provided by the team, Prof has also mentioned that it is a bug if the cutoff data cannot be seen in any way. I am unable to see the cutoff data in any way, thus I consider it a bug.

The threshold the team has to consider "extreme" inputs also seem to differ from that of the Prof, who also mentions in the same screenshot that an example of "extreme" is 1000 chars. However the team has decreased this by a factor of 10 and considered my input of 131 characters "extreme" as well.

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** This is not purely a cosmetic issue. There is no other way to retrieve the hidden information, meaning the hidden text is gone forever. As can be seen in the screenshot provided by the team on Prof's clarification, just before the highlighted part, this is considered a bug, and is not purely cosmetic.