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.
Chromium uses web search for .internal TLD instead of opening URL
71–80 of 96 posts
Re: Chromium uses web search for .internal TLD instead of opening URL
#72The 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
Re: Chromium uses web search for .internal TLD instead of opening URL
#73Earlier 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
Re: Chromium uses web search for .internal TLD instead of opening URL
#74What 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…
Re: Chromium uses web search for .internal TLD instead of opening URL
#75Earlier 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…
Re: Chromium uses web search for .internal TLD instead of opening URL
#76I gotta say, I didn't like when Google grabbed .dev, but now I like having a .dev domain =)
Re: Chromium uses web search for .internal TLD instead of opening URL
#77to 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
#78The 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
#79The first thing I do after installing a web browser is disable search for the URL bar.
Re: Chromium uses web search for .internal TLD instead of opening URL
#80The 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.