<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">This case is covered by
<a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1080682">https://bugzilla.mozilla.org/show_bug.cgi?id=1080682</a><br>
<br>
~ Gijs<br>
<br>
On 24/10/2014 13:40, Blake Winton wrote:<br>
</div>
<blockquote
cite="mid:3C2D380F-F224-4471-A147-500E081C50A5@mozilla.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
On Oct 24, 2014, at 12:58 AM, Boris Zbarsky <<a
moz-do-not-send="true" href="mailto:bzbarsky@MIT.EDU" class="">bzbarsky@MIT.EDU</a>>
wrote:<br class="">
<div>
<blockquote type="cite" class="">On 10/23/14, 10:07 PM, Projjol
Banerji wrote:<br class="">
<div class="">
<blockquote type="cite" class="">In it's current state, if I
were to write together.js in the url bar,<br class="">
it would accept it as an address and try to go to <a
moz-do-not-send="true" href="http://www.together.js"
class="">www.together.js</a> . In<br class="">
Chrome, for invalid addresses, it re-directs the user to
Google's<br class="">
result for the given query.<br class="">
<br class="">
Can this be worked upon?<br class="">
</blockquote>
<br class="">
We'll also do a search if the address is actually invalid.<br
class="">
<br class="">
It sounds like for you <a moz-do-not-send="true"
href="http://www.together.js" class="">www.together.js</a>
is actually resolving via DNS?<br class="">
</div>
</blockquote>
</div>
<br class="">
<div class="">Nope. I’m seeing the same behaviour on Nightly,
but:</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">� bwinton@11:43/mozilla-central/ $ ping
together.js</div>
<div class="">ping: cannot resolve together.js: Unknown host</div>
</div>
<div class="">
<div class="">� bwinton@8:36/mozilla-central/ $ ping <a
moz-do-not-send="true" href="http://www.together.js"
class="">www.together.js</a></div>
<div class="">ping: cannot resolve <a moz-do-not-send="true"
href="http://www.together.js" class="">www.together.js</a>:
Unknown host</div>
</div>
<div class=""><br class="">
</div>
<div class="">I think it’s more that “together.js" <i class="">looks like</i>
a host, and so we try to resolve it, and never manage to fall
back to the search. (And perhaps we shouldn’t, in this case.
I’m not sure how many people try typing things that look like
hostnames vs. make typos which they don’t want to search for…)</div>
<div class=""><br class="">
</div>
<div class="">Projjol, as a workaround, if you use “?together.js”,
it won’t do the lookup, and will jump straight to a search…</div>
<div class=""><br class="">
</div>
<div class="">Later,</div>
<div class="">Blake.</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
firefox-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>