Make Searchable Act More Like Native HTML Input

I was wondering if there were design decisions on why searchable select does not act more like native HTML inputs.

For example: 1.) ValueComponent appears to be HTML input value, but it is not. 2.) When you click the ValueComponent, you expect the cursor to appear where you clicked in the text.

I have this PR, which I need to fix (dropped .2 in coverage) and some commits ready, but before I continue: 1.) Is this something worthwhile for the community? 2.) Was this not explored for some reason?

[gojohnnygo]

@JedWatson Can you take a look this comparison and give me your thoughts at my first stab?

Summary

1. Changed behavior for searchable single select only.
2. select has a value > ValueComponent clicked (the empty space) > the input field will have the text of the ValueComponent’s label > cursor will be at the end of the text.
3. select has a value > ValueComponent’s clicked (the value label) > the input field will have the text of the ValueComponent’s label > text will be highlighted (image below). This is similar to the Facebook’s search bar behavior.

The whole input value is selected (vs putting the cursor where you clicked) bc I’m not sure if it’s worth the trouble. It seems like it can be done but won’t elegant.

With the changes above, there is one side effect to the options. When you click on the the component, the drop down activates as usual but with only one option: the value the select already has. Feature or bug? ¯_(ツ)_/¯

TODO: When component is focused, the cursor should be at the end of the value.

[gojohnnygo]

Oh yeah, I got that hotness…but for an old ver. I’m kind of busy at work atm, but should have time to fix any conflicts and do a PR next week.