Bug: using only number as search keyword doesn't work

Yes, it looks like if the browser can see the number as an IP address it will. I wonder how this is going to be fixed; IP addresses are allowed in URLs.

As of 1.0.5.16 default web browser still refuses to recognize "8888577" as search keyword. The term "8888577" is a slang on Korean baseball scene, there might be other number-only keywords in the world :(

As of 1.0.5.19, the browser doesn't accept 3.14 as a search keyword, or 2048, or 42. If you want to search for what number 13 means, you have to type "thirteen" or similar. Desktop browsers don't have this problem.

With a little testing, the browser seems to interpret any number sequence that contains a dot (e.g. "3.14", "1.2.3.") as an IP address (the address is shown in the "loading" bar above the toolbar in the bottom, but nothing is loaded). A simple number like 314 or 123 just Does Nothing, as if you didn't search at all.

I think an IP address should have (at least) four numbers separated by punctuation, right? All numbers that don't fit that description shouldn't be interpreted as IP's but treated as search engine keywords.

At least 3.14 is a valid IP address which expands to 3.0.0.14.

Edit: It seems, that other numbers could be converted as IP address, too. Here some examples from my Windows workstation in my office:

• ping 3.14: 3.0.0.14
• ping 123: 0.0.0.123
• ping 314: 0.0.1.58
• ping 2048: 0.0.8.0

Seems like (at least Windows) converts numbers into bin and uses this as IP address.