Skip to content

Added visit Site option to access custom domains (including localhost)#2700

Open
OmegaGiven wants to merge 2 commits intominbrowser:masterfrom
OmegaGiven:domain-guess
Open

Added visit Site option to access custom domains (including localhost)#2700
OmegaGiven wants to merge 2 commits intominbrowser:masterfrom
OmegaGiven:domain-guess

Conversation

@OmegaGiven
Copy link
Copy Markdown

@OmegaGiven OmegaGiven commented Apr 9, 2026

This is a simple addition to always allow a bottom action to just try and search the url entered as if it was an actual domain. this is especially useful for homelab settups and custom domains in a network for big homelabers like me

main use case is go/ is a custom domain that redirects me to different websites on any device in my tailnet and in the vanilla min browser it just treats it as a web search.

its the bottom recommended option will now always be there for those of us that need it for first time min users so that we dont have to type https://go/ manually and such

this would also give those that have issues with localhost an option to use this to override any issues with the basic interpertation and not result in a search instead
image

Issues this would cover with this as an option and is how brave browser handles it in a round about way:

#482

#2602

#2516

…s say if you are in a homelab env or setup locoal env tools that need that so it doesnt default to duck duck go
@OmegaGiven OmegaGiven changed the title added a option that you can select if you are accessing custom domain Fixed visit Site option to access custom domains (including localhost) Apr 9, 2026
@OmegaGiven OmegaGiven changed the title Fixed visit Site option to access custom domains (including localhost) Added visit Site option to access custom domains (including localhost) Apr 9, 2026
@PalmerAL
Copy link
Copy Markdown
Collaborator

This does seem like something that's worth fixing, but I wonder if this is the right solution. If we did this, every time you visited the go/ URL, you would have to tab down to the bottom to select this entry, right?

It looks like once you manually type "http://go" once, autocomplete is already able to autocomplete the "go" part if you start typing "g". The problem is that when you press enter, the original autocomplete entry is ignored, and the searchbar interprets "go" as a search instead. I'm thinking that we could update that so that we track the original URL that generated the autocompletion, and when enter is pressed, load that instead of trying to parse the text in the searchbar.

The effect would be that you would have to manually type "http://go" on the first visit, but on subsequent visits, just typing "go" would work and would be converted to "http://go" by autocomplete.

If we did that, do you think that would sufficiently address the issue, or would it still be better to have something like this to handle the case where the name has never been typed before?

@OmegaGiven
Copy link
Copy Markdown
Author

OmegaGiven commented Apr 14, 2026

I see what you mean.
Here is what brave browser does:
image

It puts it as the first option but i think it tries if its a passing dns and if fails then it will fall back to search engine. Firefox has a hard time with this but chrome is ok but I find myself having to scroll down in chrome to the dns search. So just depends on where you want it. Look at my changes or if you want to test it and let me know what you think and if we want it to be the first or last option, I just know this is a showstopper for homelab people like me to daily drive this. Also know I dont understand the min bowser deeply so maybe changes for this should live somewhere else. I just know for people that do this they want to type a custom dns and it work first time else its a pain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants