scratchfoundation / scratchfoundation/scratch-blocks
Make field input focus and numpad visibility depend on how the field was clicked
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 1.6k
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 12
Description
Right now we use user agent matching to find android/iOS and use that to determine (a) whether to show the numpad or not and (b) whether to focus the fields who have editors that use html inputs (in order to prevent the onscreen keyboard from appearing).
We should move to somehow detecting whether the field click came from a mouse or a touch, and use that information to show the number pad and prevent field focus.
/cc @picklesrus this is the issue we were discussing the best way to approach.
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.
Research direction
Start by tracing the existing user-agent matching that controls numpad visibility and focus for fields with HTML-input editors. Determine where field clicks are handled and how mouse versus touch can be distinguished; done means numpad visibility and field focus follow the click input method rather than Android/iOS detection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100