UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Example URL:
foo.test

Steps to reproduce the problem:
1. Type "foo.test" into the URL bar
2. A search will be performed

What is the expected behavior?
The domain "foo.test" should be visited.  

Furthermore, all reserved TLDs, i.e. ".test", ".invalid", ".example", and ".localhost" currently misbehave the same way, and resolution of all these domains should be corrected.

What went wrong?
A search is performed instead of visiting the domain.

Did this work before? N/A 

Chrome version: 63.0.3239.84  Channel: stable
OS Version: 10.12.6
Flash Version: 

A workaround is to specify the protocol by typing "http://foo.test" or adding a trailing slash with "foo.test/".  Therefore, I imagine there is some sort of heuristic in place for guessing what "is a URL and isn't."  I imagine the definition could be expanded where TLDs like ".com", ".org" et al are listed, to also include ".test" and friends.

This issue was surfaced here: https://github.com/ysbaddaden/prax.cr/issues/61#issuecomment-332120684  Performing a search is a really poor default for developers who are trying to use these TLDs for their intended purposes.