[iOS, Android, Web] Return on an empty list item adds another item instead of ending the list

Open
#810 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

@szydlovsky is already working on this.

Since Nov 9, 2026.

  • #859 by @szydlovsky — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
ios, react-native
Domain
mobile

Research direction

The bug is in the iOS side of EnrichedTextInput, where the return key is handled while the caret sits in an empty list item. Start by finding the return-key handling for lists and reproducing it with toggleUnorderedList() and an ordered list in the example app on the iOS simulator. Done means that pressing return on an empty bullet or numbered item removes the list marker and leaves normal text, while non-empty items still add a new item.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
In EnrichedTextInput, return on an empty bullet or numbered list item adds a new empty item below it. The user must tap the list button again, or press backspace to get back to normal text. Most editors on iOS end the list on return in an empty item, for example Apple Notes or Google Docs, which is why i think this will be perceived as a bug rather than a missing feature by the user.

To Reproduce
Steps to reproduce the behavior:

  1. Toggle an unordered list (toggleUnorderedList()) or an ordered list.
  2. Type something, press Return.
  3. The caret is now on the second (empty) item. Press return again.

Expected behavior
Return on an empty list item ends the list.

Screenshots
Screen cap: https://github.com/user-attachments/assets/3953a8c2-467d-42b0-a668-8e4c272fd0eb

Device:

  • Device: iPhone simulator
  • OS: iOS 27.0
  • Version 1.1.1
Dominant language
C
Stars
1.4k
Forks
77
Avg merge
3d 14h
Merged PRs (30d)
24

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from software-mansion/react-native-enriched-html

All issues in software-mansion/react-native-enriched-html

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.