Enatega Customer App: Cursor not visible and placeholder not updating in "Restaurant Instructions" field upon focus
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
Research direction
Start in the Enatega Customer Application and reproduce the issue at the Restaurant Instructions field after adding a product to the cart. Locate the field's implementation and check its focus behavior and placeholder handling. Done means a visible blinking cursor appears on focus and the placeholder changes or disappears while the field is active.
Written by the indexing model from the issue text.
Description
Describe the bug
When the user selects (focuses on) the "Restaurant Instructions" input field, the cursor does not appear, giving the impression that the field is not active or editable. Additionally, the placeholder text remains unchanged, which may confuse users and make it unclear that they can start typing instructions.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Customer Application'
Click on 'Restaurant' to add product in your cart.
Now see at the bottom the field to add special instructions for restaurants (e.g Mayo)
See error Cursor not visible and placeholder not updating in "Restaurant Instructions" field upon focus
Expected behavior
When the input field is selected, a blinking cursor should appear to indicate that the user can enter text.
The placeholder text should change (or disappear) to reflect that the field is now active and ready for input.
Smartphone (please complete the following information):
Device: [e.g. Infinix Hot 50]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. Latest ]
- Dominant language
- JavaScript
- Stars
- 2
- 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 patriciaperez90/react-native-based-uber-eats-clone-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2622 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
patriciaperez90/react-native-based-uber-eats-clone-app#2620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2557 ·
All issues in patriciaperez90/react-native-based-uber-eats-clone-app
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100