CATcher-org / CATcher

CATcher is a software application used for peer-testing of software projects.
https://catcher-org.github.io/CATcher/
MIT License
70 stars 68 forks source link

CATcher unable to click dropdown for "severity" #1269

Closed KhoonSun47 closed 5 months ago

KhoonSun47 commented 5 months ago

Describe the bug I am getting this error when I am creating an issue at the CATcher. So, after I typed in the title of the issue and the description of the issue, and when I wanted to choose the severity and bug type, it crashes.

To Reproduce

  1. Create a bug report.
  2. Update the title and the description of the bug.
  3. Click on the “Severity” or “Bug Type” dropdown.
  4. The CATcher crashes.

Expected behavior The "Severity" dropdown should show me the list of severities that I can click.

Screenshots

New Issue Pasted Graphic 15

Desktop (please complete the following information):

Additional context

KhoonSun47 commented 5 months ago

After restarting my laptop, and connecting to the hotspot again, I managed to select on the dropdown without crashing.

damithc commented 5 months ago

@KhoonSun47 If this happens again, use Firefox (not Chrome. This issue may be linked to the latest version of Chrome)

woojiahao commented 5 months ago

Seems like an issue with MacOS too: https://www.tonymacx86.com/threads/frequently-aw-snap-error-11-on-chrome-after-update-to-sonoma.327627/

@damithc Maybe it's good to give this preface during the PE to let them know to try this if it happens:

Some simple solutions for the Aw Snap Chrome error are reloading the page, checking your internet connection, and opening a private browser. If none of those strategies resolves the problem, you can try clearing your browser cache, disabling extensions, or updating Google Chrome.

(Taken from the link)

damithc commented 5 months ago

Thanks for the inputs @woojiahao Mine is Windows 11, so seems like it has spread to Windows as well :-p So far, the common factor seems to be Chrome.

woojiahao commented 5 months ago

Haha, that makes sense. Let me check if it's been filed with Chrome too in that case