Per Wikipedia:
> As of October 18, 2024, the domain has not been standardized by the Internet Engineering Task Force (IETF), though an Internet-Draft describing the TLD has been submitted.
Chromium uses web search for .internal TLD instead of opening URL
91–96 of 96 posts
Re: Chromium uses web search for .internal TLD instead of opening URL
#92Earlier quoted context omitted.
Right, considering that single-label names (indistinguishable from search queries) have been a thing since WINS/NetBIOS, DHCP suffixing, etc. -- expecting a dot (let alone a dot followed by a public suffix) is bogus.
Well, that wouldn't work with most search queries then. Do you really want to (fail to) load http://facebook/ when somebody types "facebook" into the address bar?
I agree most people wouldn't want that. We're talking about typing the scheme in this particular comment thread, however. Most people who type a scheme followed by a single-label name (e.g., "http://facebook") are not intending to submit a query to a search engine, so it's good that browsers don't use the lack of dot as a search heuristic in such cases.
Re: Chromium uses web search for .internal TLD instead of opening URL
#93What 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 has happened to me a couple times in the Chromium bugtracker. Another issue I filed: https://issues.chromium.org/issues/40900126 I provided a click-by-click instruction with only 3 steps. The triager created screen recordings twice, each time skipping an aspect of step 2; I wrote: > "You did not follow step (2) of my repro steps: Loading a 1 GB file form a Windows file share (network folder)." > > ... > > This t…
Lol. "Thanks..!!"
Re: Chromium uses web search for .internal TLD instead of opening URL
#94Earlier quoted context omitted.
I think it's the autocomplete in particular that leaks a lot of private data. I've rarely had the combined bar do a search when I didn't want it to. But I use firefox and I turned off autocomplete. And I use my own search instance (SearXNG)
> I think it's the autocomplete in particular that leaks a lot of private data. That’s the beauty. The whole unified input can be presented as a UX simplicity gain, while this quote points at the actual business value. ;)
Innovation!
Re: Chromium uses web search for .internal TLD instead of opening URL
#95One of the worst security bugs of browsers is the combined url/search bar. But Google loves it! What about .corp subdomains?
We had them separated once upon a time. UX was arguably worse.
I think that it does not need a separate area of the screen reserved for searching, but that there should be an explicit way to indicate that you want to search. For example, this could be a popup window. Unlike the URL, which it is useful to be displayed even if you are not entering a new URL, this is not necessary for entering search queries, so using a popup window for this purpose may be helpful.
Re: Chromium uses web search for .internal TLD instead of opening URL
#96Earlier quoted context omitted.
You’d be surprised how many folks don’t turn up their font size when they have bad vision
You'd be surprised how hard adjusting font sizes in UI elements can be.
It should not need to be, if designed well. For example, the operating system facilities could make it that UI sizes will be specified by character size instead of by pixels, and then the operating system facilities can allow the user to adjust the UI fonts, so that any programs could use them.