search

hanscau / pe

0 stars 0 forks source link

Default window size hides additional goods details #5

Open hanscau opened 2 weeks ago

hanscau commented 2 weeks ago

Understand that the UI is adjustable, however the original size of the application is too small to view all the information for the goods.

Maybe can set the default window size to be bigger such that all elements are seen on startup or move the data in such a way that it will always be seen.

Maybe an indication that there are more data that is currently being hidden due to window size.

image.png

Requires adjustments

image.png

soc-se-bot commented 2 weeks ago

Team's Response

Similar to the duplicated issue, we do see this as a concern for some users.

The 'Original' Bug

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

UI bug important Ui components were missing

Background

As i was using the software in the small screen I could not find the delivery status etc.

image.png

Test case

I tried resizing the UI and then I finally found the elements on the right side

Actual

image.png

Why this severity

This cause a lot of confusion for me as I could not find the elements at all and only found it after resizing by accident. I gave this medium as I expected the UI to be same for all sizes. Even if it is hidden it should be written in the UG to let users know that smaller UI might cause crucial parts of the UI to be missing

[original: nus-cs2103-AY2425S1/pe-interim#339] [original labels: severity.Medium type.FeatureFlaw]

Their Response to the 'Original' Bug

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

Although this would be a concern for users, it has been documented in the UG under the Resizing of UI Elements (albeit unclearly), and would only affect users who are using AB3 in a minimized layout.

Hence, we concede this is a valid oversight, and would affect some users.

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 type Team chose [`type.FunctionalityBug`] Originally [`type.FeatureFlaw`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]