dcc.Input selectionStart not functioning as expected
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Describe the bug
dcc.Input properties selectionStart and selectionEnd not updating and returning None or initial set value
Expected behavior
Expect that the values of selectionStart (or selectionEnd) will return the offset into the element's text content of the first (or last) selected character.
Screenshots
This is reported in the following community posts:
https://community.plotly.com/t/explaining-selectionstart-in-dash-input-component/39023
https://community.plotly.com/t/selectionstart-and-selectionend-doesnt-seem-to-work-for-input-not-available-for-textarea/54746
https://community.plotly.com/t/selection-in-dash-component-not-working/36707
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
No source file or test is named; start by reproducing the issue with dcc.Input and checking how selectionStart and selectionEnd are exposed. Compare the observed values with the expected text-selection offsets described here and in the linked community posts; done means both properties update and return the current selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100