search

woojiahao / pe

1 stars 0 forks source link

Scrollbar is cropped out when window size is too small #9

Open woojiahao opened 12 months ago

woojiahao commented 12 months ago

As seen in the following screenshots:

Screenshot 2023-11-17 at 16.42.23.png

Screenshot 2023-11-17 at 16.42.01.png

nus-se-script commented 11 months ago

Team's Response

It is a duplicate of 400 as the user can actually solve the problem by expanding the window.

The 'Original' Bug

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

Tags section label disappears if window is too small

May make it hard to discern what that field should be

Screenshot 2023-11-17 at 16.41.43.png

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

Their Response to the 'Original' Bug

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

Thank you for pointing this out, however, this issue is easily solved by expanding the window.

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:** This should not be rejected as it is a completely valid bug with the UI. There may be a chance that the user has display limitations making it impossible for them to scale the window to view the scrollbar. The **Rejected** status should be reserved for when missing a scrollbar is **expected and correct behavior** but by no means is having a missing UI components supposed to be expected, especially in the constraint mentioned above. Just because there's a possible fix that can be applied, does not mean that it is a universal fix (which it isn't in this case) and more can, and should, definitely be done to accommodate for this issue as well. This does not mean that it needs to have been done within the period of the TP, but certainly something that can be done as a future iteration. In fact, a screen size limitation is a completely valid concern as another report I had raised where the team had considered "CannotReproduce" because their screen could not scale any larger. The team has faced, first hand, how a limited screen real estate can make it hard to replicate and respond to bug reports, hence, I don't see how "just resizing" and **Reject**ing is a valid response to a UI bug. ![Screenshot 2023-11-21 at 12.12.37.png](https://raw.githubusercontent.com/woojiahao/pe/main/files/d1581afa-e43e-4012-9572-3dece04a25fb.png)