# SelectionStart and SelectionEnd: Doesn't seem to work for Input / Not available for Textarea

**URL:** <https://community.plotly.com/t/selectionstart-and-selectionend-doesnt-seem-to-work-for-input-not-available-for-textarea/54746>\
**Category:** Dash Python\
**Created:** [July 14, 2021, 6:08pm UTC](https://community.plotly.com/t/selectionstart-and-selectionend-doesnt-seem-to-work-for-input-not-available-for-textarea/54746 "2021-07-14T18:08:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnW](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@JohnW](https://community.plotly.com/u/JohnW)\
**Post date:** [July 14, 2021, 6:08pm UTC](https://community.plotly.com/t/selectionstart-and-selectionend-doesnt-seem-to-work-for-input-not-available-for-textarea/54746/1 "2021-07-14T18:08:10Z")

</div>

Hi.

There seems to be an issue with selectionStart (and/or -End). Supplying them as a callback Input or State only ever gives me the initial value (provided I had set one explicitly in the layout). I’ve been trying numerous variations of code that are all basically like adamschroeder’s [here (topic 39023)](https://community.plotly.com/t/explaining-selectionstart-in-dash-input-component/39023). Am I (are we) missing something?

Also, I ultimately will need to use this functionality in a Textarea also, but I only see this property associated with Input. That seems like an odd asymmetry. It’s arguably even more useful in a Textarea where people might be expected to do more complex editing etc - you know, as I am literally doing as I type this. 😉 In fact, my goal is to put some Markdown buttons on my Inputs and Textareas not unlike what is on this very widget.

Thanks a bunch!  
John