For instance, if I partially type the search and then select a suggestion, the full suggestions does not replace the partial text in the search box.
This is by design. Does your app have a requirement for displaying the suggestion in the text input?
Yes because it also affects the directions widget....so now your start and/or finish stops only show the partial text.
Sent from my T-Mobile 4G LTE Device
Hmm...Interesting. Could you provide a link to a small sample reproducing this issue so we can take a look at it some more?
Hi Kristian, Michael Stranovsky is across the wall from me, here is a link to the site:
Select the directions widget from the onscreen icon and begin entering a facility name, such as 'Little Bob' into the first search window. You should immediatly see that the name does not fully complete.
At 3.16 of the API, the auto-complete function of the Search contained within the Directions widget has no issue. If you wish, I can go in and change the site to use the 3.16 library after you reply-
Thanks, David. It looks like you're still able to get a route. It's just the text that isn't displaying the way you want it to. I tried testing with 3.16 and it looks like it has same behavior as well (for Search widget only). I didn't test with directions widget. Can you use 3.16, so I can take a look at it?
Hi Kristen, yes the routing is working just fine at 3.17, and when searcing an address, the address fully auto-completes, its just the feature layer search return. I have set the app back to 3.16 and you should see a full auto-completed text in the search dialogs
Michael Stranovsky David Coley
We'll look into this. Can one of you submit a bug report or enhancement request to Esri support so we can log this issue into our system and so you can also track its progress?
Hi Kristian, yes I'll get that logged shortly - thanks for your help
Support case started, thanks-
It's a bug:
Retrieving data ...