3 ms·
>for example, when I type `localhost` in my nav bar, Chrome autofills the port; FF doesn't (it just puts `localhost/`, which is useless). What? Isn't it the op
by thiht 8y ago
>for example, when I type `localhost` in my nav bar, Chrome autofills the port; FF doesn't (it just puts `localhost/`, which is useless).
What? Isn't it the opposite? I have the exact opposite experience with Firefox and Chrome, FF autofills the ports and Chrome doesn't oO
I just checked it right now to be sure I reminded correctly
- ztoben 8y agoNot sure about firefox, but localhost definitely autofills localhost for me in chrome.
- myfonj 8y agoI have opposite experience with Chrome as well: I like when URL bar behaves just like URL bar and does nothing extra. I worked in company that used custom TLD for all sites in internal network, and every single time I entered such `site.tld` in Chrome's URL bar it insisted on _searching_ for that instead of just appending protocol, '/' path and visiting it like reasonable browser. To be honest, Firefox likes to mess with input too, but it can be easily tamed with few prefs, namely: keyword.enabled=false // no implicit searching from URL, must use explicit keyword or Searchbar browser.fixup.alternate.enabled=false // this prevents trying www. … .com or other configured suffixes when domain-like URL fails browser.urlbar.trimURLs=false // do not hide protocol and slash browser.urlbar.filter.javascript=false // bookmarklets FTW