barelyhuman / barelyhuman/preact-native
improve keyboard handling by queuing and drafting a keyboard text change request
- Dominant language
- JavaScript
- Stars
- 157
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently due to the type of events passed from the React Native SDK, we only have either the keys that are being pressed or the original text during focus and blur.
We don't have a way to get if the text was modified over time (by autocomplete, autocorrect) or was replaced by selection, which aren't passed as events (at least not from the simulator)
which makes it hard to write an event based keyboard handler and so needs the focus and blur handlers to find the value
React Native handles this somehow, and we don't have the full idea of it but need to figure that out.
Contributor guide
Research direction
Start by tracing the React Native SDK events available during keyboard input, along with the existing focus and blur handling. Compare this with how React Native handles text changes, especially autocomplete, autocorrect, and selection replacement. Done means the keyboard handler can observe text modifications over time rather than relying only on focus and blur values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100