Someone PLEASE explain why chrome keeps doing this
-
Any time I search for C# [insert search term] Chrome keeps doing the bullshit pictured below, where it will show the correct search term in the omnibar, but have the C/# highlighted below, and when I search it ninja edits my omnibar search for the C/# search and returns a network error.
It's beyond frustrating.
-
-
i don't know why it does that but it seems to have started around Chrome 32.
it's to the point where i just type
google.com [whatever i want]into the omnibar. I even have a macro that automatically pasts that in there if that's the window element that has focus and it's currently empty (thank you accessibility hooks in M$)
-
Fucking fuck.
Any idea how/when/where I can get this early? It's hugely frustrating.
Filed under: Why does it add a slash to my pound sign!
-
I wish the Awesome/Omni bar stuff would die out and give me a normal address bar. If I wanted to search I'd use a search engine or the search widget right freaking next to the address bar!
-
I wish the Awesome/Omni bar stuff would die out and give me a normal address bar. If I wanted to search I'd use a search engine or the search widget right freaking next to the address bar!
Yeah and those damned newfangled internal combustion cars! Why, I asked around for a downtown stable, and they laughed at me. Laughed!
-
The omnibar was working just fine before chrome 36, but whatever they did in 36 has had huge issues for me. (I still fucking want my god damned home button, and refresh button on mobile)
-
The thing is broken though. If I want to go to http://some-intranet-machine:8080/ most of the time both Chrome and Firefox decide to web search that instead of using the legitimate address I provided, and intranet browsing becomes frustrating and nearly impossible depending on the browser's mood. There's a search bar 8 pixels away from the Awesome Bar, I don't see why the Awesome Bar needs to do both.
-
Why does Chrome keep doing this? Because omniboxes are broken by design. Addressing and search are simply not the same thing, and this remains true despite the tendency of people who know no better to type "google" into browser search boxes.
-
I'm just sayin' sometimes you just gotta realize your fighting the tide, buddy. And you can't win. It's the tide. That fucking sandcastle's going DOWN, man.
-
I wish the Awesome/Omni bar stuff would die out and give me a normal address bar.
You can kill Firefox's address bar search feature by setting keyword.enabled to false in about:config.
-
I'm just sayin' sometimes you just gotta realize your fighting the tide, buddy. And you can't win. It's the tide. That fucking sandcastle's going DOWN, man.
What about his fighting?
-
Let me just jump in here to save Blakey the trouble of pointing out that removing options wherever possible is sound software engineering, and leaving them in when focus groups don't tell you to is a sign of weakness.
Personally I'm glad Mozilla retains some signs of weakness.
-
The omnibar was working just fine before chrome 36, but whatever they did in 36 has had huge issues for me. (I still fucking want my god damned home button, and refresh button on mobile)
At least it seems they didn't go for the "hide the address" thing...
-
Wow... I've been fighting this for awhile myself. Glad I'm not the only one to consistently beat my head against this.
-
Because omniboxes are broken by design. Addressing and search are simply not the same thing...
Perhaps a good dose of Markdown would help the browser distinguish between the two!
-
This is easily fixed:
Change your computer's name to c
Install and setup Apache if not already
Add/modify the public_html .htaccess file so that it redirects all http requests to https://www.google.com/search?q=c%23
-
This is what I do:
- Set default search engine to DuckDuckGo
- Type in
!gfollowed by whatever I want to search for
- ???
- Profit!
-
This is easily fixed:
Change your computer's name to c
Install and setup Apache if not already
Add/modify the public_html .htaccess file so that it redirects all http requests to https://www.google.com/search?q=c%23Can't I just use jQuery?
-
Yeah or DNS or hosts but my way is more enterprisey.
-
This is easily fixed:
Change your computer's name to cInstall and setup Apache if not already Add/modify the public_html .htaccess file so that it redirects all http requests to https://www.google.com/search?q=c%23
-
... dude.
Why the fuck.
Just edit the host file to make c/ point to google with C#
But that just compounds wtfery
-
Oh look the dog is back ...
-
the dog is back.
would you have prefered me choose a different image meme?
-
Not for long, he's noping the fuck out.
-
I would like it if you centered the text like a proper meme.
-
Just edit the host file to make c/ point to google with C#
Although I too gave that as an alternative, now that I think about it I don't believe you can point to a URL in the host file, just IPs.
And having your computer called c is a gift that will keep on giving. Try not to be so negative.
-
I generally point the http:// version of my sites that i'm developing at my local machine, and www at the remote location, so I know that's a false statement.
-
I would like it if you centered the text like a proper meme.
dirty secret, that';s where all my image memes come from
also that dog i used is pretty darned old and has been around for ages! i think it predates cheezburger.com and their black bordered monstrosities
-
-
I generally point the http:// version of my sites that i'm developing at my local machine, and www at the remote location, so I know that's a false statement.
Do you mean
127.0.0.1 matches.com? That doesn't redirect to particular page, just the IP.
If you meant74.125.230.101/search?q=c%23 c/: That doesn't work.
If there's a way to make it work I would be very interested to hear it.
Edit: Although I could believe Google have a different IP address for every search.
-
Chrome 40
I just realized, Chrome should reach version 100 by 2022, in approximately 8 years. Hopefully TheDailyWTF will still exist by then, I want to throw a party in celebration of pointlessly big numbers.
-
I think it's possible Chrome's versioning is exponential, not linear. We're simply early enough in the process that the graph still looks linear, but it'll be 10e3290472396y98324 before you know it.
-
but it'll be 10e3290472396y98324 before you know it
I don't understand the y but then we should throw a party when it reaches version googol.
-
-
Version number progression shouldn't make complete sense.
-
we should throw a party when it reaches version googol.
and another the following week when it reaches version googolplex
-
And after that, Graham's Number?
-
A mole of versions?
-
You can kill Firefox's address bar search feature by setting keyword.enabled to false in about:config.
This has been so much trouble lately that I actually took the three and a half seconds to fix it. Of course, the next version of Firefox will probably remove this configuration option altogether in order to route everything you type through ask.com malware.
-
You can have your home button on desktop. Just gotta find the setting:
-
Oh my fucking god, thank you.
-
Now do the refresh button for mobile!
-
For me, it's hidden in the weird vertical ellipsis menu. No settings to get it there, they just moved it.
-
No problem.
-
That's not an ellipsis.
That's clearly a
.
-
So first hamburgers, now traffic lights?
-
I mean, put it back in the title bar. I don't want it in that menu.
-
Sorry. I haven't found any settings for that. :'(
-
Filed under:
