Search box to database problem (is this a bug?)

@jeffmccutcheon, I have a support email thread going with @malcolm about this. I am having a rough time trying to reconcile:
the text I actually type in a search box,
the options output in the dropdown below the search box,
and the actual value that is automatically selected by a geographic search box when the box is unfocused, or another operation is performed, like your app sending an address to a database.


(Typed text is ‘san’, dropdown shows ‘Santiago’, actual value is ‘San Diego International Airport’)

I’d like to see ‘typed text’ exposed in the case of geo searches, if possible.

I think it might be possible to find this exposure using regular inputs and groups, but the search box has a lot of great features, like typeahead, tab and arrow keys functionality, and the built-in dropdown, that I’d like to avoid cobbling together myself.