Live data from Hacker News

Chromium uses web search for .internal TLD instead of opening URL

issues.chromium.org

71–80 of 96 posts

Re: Chromium uses web search for .internal TLD instead of opening URL

#71
post #21

Earlier quoted context omitted.

I have them separated in firefox because i find it superior.

I have it too, but unfortunately this only gives you two search boxes, behavior of the url bar doesn't change.

I'm pretty sure that you can fully disable search in the URL bar by changing 'browser.fixup.alternate.enabled' to false

Re: Chromium uses web search for .internal TLD instead of opening URL

#72
post #48
post #47

The first thing I do after installing a web browser is disable search for the URL bar.

Is that even possible? I agree that it should be the default behavior. ..maybe I can set up an own mock search service on localhost. Hmph, I will think about it

afaik you can use prefix to explicitly do search. for example no direct search but you can use "g paris" to search for paris on google or "w paris" to search paris on wikipedia

Re: Chromium uses web search for .internal TLD instead of opening URL

#73
post #50

Earlier quoted context omitted.

IIRC there is no setting in Firefox to keep the content of the URL bar local.

How could searchengines provide suggestions without your browser sending the url-bar content? If you want the content of your URL bar to stay local you should disable suggestions

[deleted]

Re: Chromium uses web search for .internal TLD instead of opening URL

#74

What a bizarre response from Google, a couple hours after this was posted: > @Reporter: As we are not very clear about the issue being faced by you, could you please elaborate on the same by providing detailed manual repro steps to reproduce the issue from our end. > Also requesting you to share the expected, actual behaviours along with screen-cast for better understanding of the issue. > *Note: Requesting you to co…

This kind of reply is why I can’t be bothered to report bugs anymore in general - between you and the people who know how to solve the problem there are five layers of bureaucrats who want to waste your time by bouncing the ball back into your court and asking for completely irrelevant details.

Re: Chromium uses web search for .internal TLD instead of opening URL

#75
post #52
post #30

Earlier quoted context omitted.

probably just an ai or unskilled triage tech responding?

I'd tend towards the latter, AI would have been more wordy and polite (it would have written "Also, please share" instead of " Also requesting you to share"). Sounds like someone just had a desire to make this pesky bug report go away, requesting detailed version information, detailed steps to reproduce, expected behaviour and a screencast (!), hoping the reporter wouldn't provide them so they have an excuse to close…

[deleted]

Re: Chromium uses web search for .internal TLD instead of opening URL

#77
The whole local development is still a big mess. I recently starting using

http://subdomain.localhost

to keep different projects apart during development only to realize that you can't make that work with OAuth, because you can't use http://subdomain.localhost as a Oauth callback host. But you also can't share cookies between subdomain.localhost and localhost to redirect back without losing the session.

Re: Chromium uses web search for .internal TLD instead of opening URL

#78
post #77

The whole local development is still a big mess. I recently starting using http://subdomain.localhost to keep different projects apart during development only to realize that you can't make that work with OAuth, because you can't use http://subdomain.localhost as a Oauth callback host. But you also can't share cookies between subdomain.localhost and localhost to redirect back without losing the session.

Nothing stopping you from redirecting a code response redirect from the authorization server. Have a shim server return 302 from `http://localhost/subdomain/oauth?code=...` to `http://subdomain.localhost/oauth?code=...` for example.

Re: Chromium uses web search for .internal TLD instead of opening URL

#79
post #47

The first thing I do after installing a web browser is disable search for the URL bar.

The other thing I do is disable history. I forget the flag in Firefox (might be places.history.enabled or something). Forward and backward navigation still work per tab, but nothing gets recorded in the history menu. Every once in a while I wished I could go back into my history, but overall I prefer not to leave a log of what pages I've been to.

Re: Chromium uses web search for .internal TLD instead of opening URL

#80
post #77

The whole local development is still a big mess. I recently starting using http://subdomain.localhost to keep different projects apart during development only to realize that you can't make that work with OAuth, because you can't use http://subdomain.localhost as a Oauth callback host. But you also can't share cookies between subdomain.localhost and localhost to redirect back without losing the session.

Nothing stopping you from redirecting a code response redirect from the authorization server. Have a shim server return 302 from ` http://localhost/subdomain/oauth?code= ...` to ` http://subdomain.localhost/oauth?code= ...` for example.

Need to try this.
Post reply on HN