Live data from Hacker News

Chrome redirecting to blank.html on search

productforums.google.com

81–90 of 117 posts

Re: Chrome redirecting to blank.html on search

#81
post #57
post #30

Crazy that this broke, but an interesting reminder of how annoying browsers were when you had to type "www.google.com" before you could search.

Well let's not forget that before this the norm was a search box that was placed next to the address bar. Just saying :p

Right, where (in Firefox) you could just hit ctrl+k / cmd+k to get the cursor into the box (as opposed to ctrl+l / cmd+l to get to the omnibox). Not that much more difficult.

Re: Chrome redirecting to blank.html on search

#83

Regarding all the suggestions to change search engines: Deleting the Google search entry is not an action that can easily be undone, and it will have drastic consequences, such as permanently disabling suggestions and instant for omnibox searches. Creating an alternate entry with the same URL does NOT suffice -- you can't manually enable any of this functionality on the alternate entry. If you're having this bug, I s…

That sounds anti-competitive. So is there a reason other search providers aren't being allowed the opportunity to support this functionality?

It does, especially since I think IE and possibly Firefox allow other search providers to do this.

Re: Chrome redirecting to blank.html on search

#84
post #45
post #40

Earlier quoted context omitted.

If you're going to go to that much trouble anyway, may I suggest using: https://encrypted.google.com/search?q=%s A little bit more privacy, a little bit less trackable (And, for this crowd, I should point out it'll strip the search query from the referrer when you click the search links in the ssl version of Google's SERPs - so the Google Analytics (or any other analytics tools) won't have those inbound search query…

Unfortunately seems to be US-only: > The server at encrypted.google.com.au can't be found, because the DNS lookup failed thanks for the tip though, still going to go with this.

Earlier this year Google announced that they will roll out HTTPS-by-default to all localized Googles. I guess they haven't got it done yet. http://insidesearch.blogspot.com/2012/03/bringing-more-secur...

Re: Chrome redirecting to blank.html on search

#85
post #16

From the giant thread, user BolshoiBrit: Found a work around: Add a new a search engine in wrench >> settings >> search "Manage Search Engines". Under "other search engines" add a new search engine using this address for the URL http://www.google.com/search?q=%s Name it "Google 2" or whatever you want. Works like a charm. -B

I suggest trying DuckDuckGo, a search engine that doesn't track you. Same instructions but replace the search url with: https://duckduckgo.com/?q=%s

Unfortunately DDG's results suck. Nobody really cares about Google's 'tracking', people use them because they work.

Re: Chrome redirecting to blank.html on search

#86
post #64
post #36

Earlier quoted context omitted.

Your answer explained why it is helpful to google. It does not explain why individuals post "me too," or why people are posting "me too" here on the HN page... There is a similar behavior here on HN with nice- page / I-agree / congrats posts. I'm wary of a general guideline that I should only post to HN if I think the karma reward will be greater than X, but more often than not I think it helps make sure any of my po…

His answer explains that as well. Since the per post karma have been removed the only way to show you agree is to write an "I agree" post. If I upvote it only the author will see that someone upvoted it, but it is also information that is valuable to others. Hence, the only way to truly support a comment is to write a "me too" or try to rewrite "me too" into some rambling as if you had something else to contribute wi…

"Me too" is often used as a way to bump a forum thread back to the front page of forum software so that mods and others can have time to participate before the thread rolls off into murky ancient history. For instance, you very often see this in game forums.

Now, my pet theory is that game forums seeded this behavior, and now more people use it even on forums where it is technically unnecessary.

That said, I wonder what the game theoretical explanation is.

Re: Chrome redirecting to blank.html on search

#88

Earlier quoted context omitted.

I suggest trying DuckDuckGo, a search engine that doesn't track you. Same instructions but replace the search url with: https://duckduckgo.com/?q=%s

Unfortunately DDG's results suck. Nobody really cares about Google's 'tracking', people use them because they work.

Interesting, what makes you say that DDG's results suck? I've been using it as my primary search engine for a few weeks now and aside from it not including a map in results unless you give it a very explicit address, I've found it no worse than Google's results.

Re: Chrome redirecting to blank.html on search

#89

Regarding all the suggestions to change search engines: Deleting the Google search entry is not an action that can easily be undone, and it will have drastic consequences, such as permanently disabling suggestions and instant for omnibox searches. Creating an alternate entry with the same URL does NOT suffice -- you can't manually enable any of this functionality on the alternate entry. If you're having this bug, I s…

LOL. Somehow I'm not surprised that Chrome has an aneurysm if you delete the Google search entry.

Re: Chrome redirecting to blank.html on search

#90
StoneImp has a better solution altogether:

Lol, I figured it out. in the original google url box it has this for some reason

{google:baseURL}search?{google:RLZ}{google:acceptedSuggestion}{google:originalQueryForSuggestion}{google:searchFieldtrialParameter}sourceid=chrome&ie={inputEncoding}&q=%s

The trial is not capitalized! Convention got broken, lol. If you want your omibox to work exactly like before

Go to Wrench >> settings >> search "Manage Search Engines". Under "other search engines" add a new search engine using this address for the URL Name: Google2 Keyword: google URL: {google:baseURL}search?{google:RLZ}{google:acceptedSuggestion}{google:originalQueryForSuggestion}{google:searchFieldTrialParameter}sourceid=chrome&ie={inputEncoding}&q=%s

Credit to BolshoiBrit for figuring out part of this, just wanted to publish this one level higher to help people

http://productforums.google.com/forum/#!topic/websearch/80Gc...

Post reply on HN