Mobile devices cannot add tags - enter does not submit tags but instead moves to next form field
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start by reproducing the issue on a mobile device using the shown TagsInput configuration, then trace how addKeys and Enter key events are handled. Done means pressing Enter adds the entered tag on mobile instead of moving focus to the next form field, while preserving the existing desktop behavior.
Written by the indexing model from the issue text.
Description
<Form.Group controlId="formBasicEmail" className={styles.appFormgroup}>
<Form.Label className={styles.appInfolabel}>{label}</Form.Label>
<TagsInput
className={styles.appTagsblock}
onChange={onChange}
onChangeInput={onChangeInput}
inputValue={inputValue}
value={value || []}
maxTags={8}
addKeys={[9, 13]}
maxlength="16"
{...props}
/>
{touched && invalid && (
<div
className="signerror"
>
{error}
</div>
)}
</Form.Group>
Works fine on computer/browser. On mobile enter will only go to the next field and not actually submit the tags.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 olahol/react-tagsinput
-
prop-types is required at runtime but only listed in devDependenciesPossibly taken @Tanishdete333 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
olahol/react-tagsinput#229 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
olahol/react-tagsinput#199 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
olahol/react-tagsinput#223 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
olahol/react-tagsinput#222 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 38/100
olahol/react-tagsinput#217 · 1 comment ·
All issues in olahol/react-tagsinput
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PhyberApex/slds-json-schema-renderer#372 ·
Maintainers usually reply within 1 day
-
usage: a custom provider's balance meters ("…%" in the balance path) ignore the Left/Used switchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[BUG] rag: sentence content can cross the reported sentence boundariesPossibly taken @LJK-ikun claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ericcornelissen/depreman#591 ·
Maintainers usually reply within 1 day
-
bug/1-unconfirmed kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
prisma/orm#30818 · 1 comment ·
Maintainers usually reply within 1 day