Meteor-Community-Packages / Meteor-Community-Packages/meteor-autocomplete
Clicking around the input and changing cursor position does not change autocomplete filter
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 350
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
Changing the cursor via mouse does not update the autocomplete menu (due to this being handled in the `onKeyUp`) function of the `AutoComplete` class. The only other place this logic is also triggered is in `onFocus`.
We can simply add an `onClick` handler to tackle the basic case of this, but it requires more thought to decide what to do for drags and selected regions. Maybe the autocomplete should just go away during that time.
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 with the AutoComplete class and compare the existing onKeyUp and onFocus handling described in the issue. Reproduce the behavior by moving the cursor with the mouse, then determine the intended behavior for clicks, drags, and selected regions. Done means cursor-position changes produce the expected autocomplete behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100