Thanks for your report - I can't reproduce this with the information given. I tested with Chrome 70.0.3538.67 and Chrome 72.0.3584.0 (i.e. current Stable and Canary) on 10.13.6, and in both cases I observed that typing "Google&Google" into the omnibox led to a search for "Google&Google".

Some details that might help:
* What version of Chrome are you using? Check chrome://version
* What version of macOS are you using? Check the Apple Menu -> About This Mac
* What is your default search engine set to? Check chrome://settings/searchEngines for this - the important one is in bold, and it would be especially useful to know the "Query URL" for it

Thanks!

I have a feeling it might be the query URL after you mentioned it as I changed it manually. 

* What version of Chrome are you using? Check chrome://version

69.0.3497.100 (Official Build) (64-bit)

* What version of macOS are you using? Check the Apple Menu -> About This Mac

Sierra - 10.12.6 (16G1510)

* What is your default search engine set to? Check chrome://settings/searchEngines for this - the important one is in bold, and 

http://www.google.co.uk/#q=%s

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

#4: Yup, the custom URL is at fault here. Since the part after the # (the 'fragment') is never actually sent to the server, we do not URL-escape the & that appears in it, and the javascript on http://www.google.co.uk/#q=%s ends up redirecting you to "http://www.google.co.uk/search?q=foo%20&%20bar&cad=h", which is not well-formed - the part after the & will be treated as a separate query parameter and ignored.

You should change your custom URL template to something like:

  https://www.google.co.uk/search?q=%s

and then everything should work well :)

I'm calling this WontFix since it is not a Chrome bug.