That's different... That's just the standard UX of their mobile autocomplete. It's the same on iOS (I type "f" and it autofills a URL - next letter I type is ap

That's different... That's just the standard UX of their mobile autocomplete. It's the same on iOS (I type "f" and it autofills a URL - next letter I type is appended to the end of that URL, slash and all). This is a problem with how it's interpretations the encoding of characters - they should be escaped by default and be able to be enabled with a flag if there's a valid use for them.