Hacker News Reader

Comment by dec0dedab0de | Hacker News Reader

Separate address and search bars is old-fashioned.

Exactly how I like it, I HATE getting search results when I make a type-o, or try to go to an internal site and forget to specify http://

View on HN

Indeed. I love seeing Mozilla true to their mission. By separating them, the user knows where their input is going at all times. Only Firefox gets to see what you are typing in your address bar. Moreover, I love you can click ctrl+k in a tab, then type something you are reading on that page and then hit alt+enter to open your search result in a new tab.

I agree on the separation of input fields, but wanted to point out that the search functionality you mention exists in Chrome too (Mac equivalent in parens):

ctrl(cmd)+l to focus omnibar, alt(shift)+enter to open results in a new tab

I think for some time already you could also just select text on a page, right-click and choose "Search <search engine> for 'Lorum lipsum'" and it will open a new tab for it with your set search engine searching for that term.

I use this all the time, small thing but it's awesome! I'm pretty sure it exists in other browsers as well though.

You will then probably also like to set browser.fixup.alternate.enabled to False in about:config, to disable the trying to go to 'whatyoutyped.com' and such when hitting an NXDOMAIN.

Me too! accessibility.typeaheadfind.flashBar=0 --- browser.fixup.alternate.enabled=false --- keyword.enabled=false

Turns the address bar into an ACTUAL address bar. (Hope I didn't forget any.)

For anyone who reads this later, it might be helpful to clarify that the kind of settings you're referring to there are for things like adding missing http://, www. or .com to an address. That is, while they do modify what you type if the initial response is negative, they're quite different to the send-every-character-you-type behaviour used for autocomplete in a search box (or anything at all, in browsers with unified URL/search boxes).

Not sure about firefox, but in chrome you can get around it by appending a trailing / to things

Thanks, that worked for me in Chrome for desktop, but not in my Android mobile browser which messes up intranet site addresses even if I select them from history.

Android always uses googles DNS settings.

See answer 1, manually set your DNS server in wifi Advances page.

Trailing slash works in all browsers.

I believe Safari solves this on iOS/Mac by treating the address bar as the "search option" - whether that's your memorised URL, stored bookmarks, google, history or (and my favourite...) the page.

Like the chap above your comment, I absolutely despise having the Firefox differentiation because my habit is to click the address bar and then depending on whether I have realised the mistake before/after hitting enter it's: (1) "S&%^ I have clicked the wrong one, <tab>" (2) "FFS I didn't want http://byron burger locations"

Well, in SeaMonkey (another Mozilla suite), when you type in the address bar (there is no search bar), there is always the suggestion to search for what you are typing at the bottom of the suggestions. But it does not provide you with suggestions.

Also Safari on iOS send the type ahead information for search suggestions. By default. Even in Private Browsing mode. And the switch is all or none.

it happens only when you omit or mistype the gTLD (the smallest part of the address). otherwise chrome shows "website not found" page.

unless you make more gTLD typos than your search queries, the mechanism works great.

You made a typo!

Reply on news.ycombinator.com