CATcher-org / CATcher-org/CATcher

'arrow_back_ios' is shown instead of a button which leads me back to the previous page

Open
#1,072 3 comments 0 reactions 0 assignees View on GitHub
category.Bug
Dominant language
TypeScript
Stars
92
Forks
85
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
This seems like a UI bug, where moments after I click on the default session to login to, I see a view where there is some text rendered called 'arrow_back_ios'. It seems like it could be a CSS classname that is being rendered, but this warrants further investigation. I think that a button should instead be rendered, leading the user back to the previous page, which was the Login page.

**To Reproduce**
Steps to reproduce the behavior:

1. Start the app from the master branch.
2. Attempt to log in.
3. When logging in with your GitHub account, it momentarily displays a view as shown below where the client is awaiting for the response from GitHub. At the current moment, the CORS issue as linked by #1070 is still not allowing me to complete my authentication and authorisation to use the default catcher account.

image

**Expected behavior**
A normal 'Back' button should be rendered instead.

**Desktop (please complete the following information):**

- OS: macOS Monterey
- Browser: chrome

**Additional context**
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the GitHub login flow described in the issue and inspect the view shown while the client awaits GitHub's response. Trace where the literal “arrow_back_ios” is rendered; done means that state displays a normal Back button returning to the Login page.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.