Incorrect interpretation of autocomplete ending with space

[missinglink]

In live mode, inputs ending with a space are considered 'complete'

This is incorrect and causes issues for queries such as:

New South (note the trailing space)

Expected: New South Wales

[bdmapman]

@missinglink in my case I am using /v1/autocomplete?text=Pizza Hut&size=5 which also considering only pizza and space occuring error. if I use /v1/autocomplete?text=Pizza%20Hut&size=5 its returning null. if using only pizza like this /v1/autocomplete?text=Pizza&size=5 then returning all expected Pizza Hut. How to search a keyword with space in autocomplete endpoints???