search

AdityaB4 / pe

0 stars 0 forks source link

Menubar help window moves to the corner of the screen when opened again #3

Open AdityaB4 opened 7 months ago

AdityaB4 commented 7 months ago

Steps to reproduce:

System details:

Screen recording:


video:https://raw.githubusercontent.com/AdityaB4/pe/main/files/6d2e8cf7-c39d-4fc1-bdb2-482f4c288272.mov

nus-pe-bot commented 7 months ago

Team's Response

None of us were able to reproduce this across windows and macbook :(

The 'Original' Bug

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

Menubar help window is blank for a couple of seconds when opened again

Steps to reproduce:

  • Click on the Help button in the menubar
  • Click the Help option in the dropdown menu
  • Close the popup menu
  • Repeat the previous steps, and from the second time the popup menu will initially open blank

System details:

  • MacBook Air M1
  • MacOS Sonoma
  • Using an external monitor
  • Laptop display shut

Screen recording:


video:https://raw.githubusercontent.com/nus-cs2103-AY2324S2/pe/master/files/19a78e1e-108d-451b-b962-495f9fb6ee20.mov

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

Their Response to the 'Original' Bug

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

Noted the issue on your end. However, no issue on our side for Windows and MacOS, works perfectly fine.

Anyways, this still meets our NFR requirement that “The response to any command should become visible within 5 seconds.”, hence we feel we should not be penalised for it.

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: Since the cause of this issue, or the one that it has been marked as a duplicate of is unclear, I believe there is liberal use of marking duplicates here.

The issues are reported separately since the blank screen and the sudden movement of the window are 2 separate behaviours.

Moreover, I believe a reasonable effort to reproduce was not made here since this is a bug that was inherited from AB3, and can be reproduced on all MacOS systems. I've attached a screen recording of me reproducing this for both AB3 and Realodex, on my teammate's macbook (M2 Macbook Pro also running MacOS Sonoma): AB3


video:https://raw.githubusercontent.com/AdityaB4/pe/main/files/5fb44821-e142-4c10-a9e8-89c34dc5157d.mp4

Realodex


video:https://raw.githubusercontent.com/AdityaB4/pe/main/files/310051d9-4de1-4f06-a0a8-1e3ff160591c.mp4

## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** I disagree that this is out of scope since it creates unintended states in the app that: 1. Cause the app to look like it is not developed to a professional standard with buggy behaviour 2. Can cause confusion for users from the unexpected behaviour