Open Andrew-Clement opened 7 years ago
We don't actually have autocompletes or submitter postcode, only for postcode of location in route, I believe (correct @agamba ?).
However, this is a bug - we should be clearing the autocomplete binding any time the dropdown is changed...
Fixed in 93a22713d40ccf5ce10100485530b8137109771c
We now remove the autocomplete binding if we have no autocomplete data.
OK, I see that there is now no auto complete for Submitter postal code, but I'm puzzled as to why there is one for regular Postcode, especially when it appears to to produce odd results. An "M6" produces many options including my own , but then searching on them finds no routes.
On 2017-04-02, at 4:37 AM, colinmccann notifications@github.com wrote:
We don't actually have autocompletes or submitter postcode, only for postcode of location in route, I believe (correct @agamba ?).
However, this is a bug - we should be clearing the autocomplete binding any time the dropdown is changed...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
@agamba would need to answer this - it's a backend question.
Perhaps autocomplete looks for any fragments of the string, but the query requires an exact match?
It appears to refer to CC instead: