Implementation of Loading Indicator for Phone Number Verification Page Transition
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reproducing the phone number verification flow in Chrome and identify the page or component responsible for the transition after submission. Add the requested loading feedback and verify that it appears while processing and is absent once the next page loads.
Written by the indexing model from the issue text.
Description
Describe the bug
Currently, there is a lack of a loading indicator when users enter their phone number for verification on the Multivendor Food Delivery site. This absence of visual feedback may lead to uncertainty about the status of the verification process, causing a potential user experience issue.
To Reproduce
Steps to reproduce the behavior:
Visit the Multivendor Food Delivery site.
Navigate to the phone number verification page.
Enter a phone number for verification.
Observe the absence of a loading indicator during the transition to the next page.
Expected behavior
A loading indicator should be implemented to provide users with visual feedback during the transition to the next page after entering their phone number for verification. This will help users understand that the system is processing their input.
Screenshots
loading.indicator.mp4
Desktop:
Browser: chrome
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lambertf917/open-source-document-solution-system
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in lambertf917/open-source-document-solution-system
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100