Hacker News Reader

Comment by jancsika | Hacker News Reader

At least in a virtual terminal window, I'm fine with any of the reported latencies as long as the input stream is handled deterministically.

What I can't stand is typing "f" then pressing "<Enter>" in the url area of a browser, and the browser interpreting the url as "f" because "f" won the race against autocomplete's return value of "https://foo.com". Just hand "f" off to autocomplete and navigate to whatever the return value happened to be.

Of course it's a browser, so I'm sure someone could exploit my desired behavior to somehow mine cryptocurrencies in a hidden iframe.

View on HN

Also when you type into a search field and the thing you want comes up as a succession, you go to click/tap and exactly at that moment, a different suggestion takes its place as the remote site catches up. Twitter is very bad for this.

This is a UI/UX felony. Anybody who writes an interface that does this should go to UI jail.

One of the reasons i go hunt for the "search suggestions" toggle the moment i use a newly installed browser.

UI determinism to me is vital, no matter how ugly it may look to designers.

And then you have to remove the search for "f" from your history or else it will try to autocomplete it in the future. I hate that! Happens to me all the time.

This seems like a Chromium derived behavior, as i have never seen Firefox do it but noticed it on Vivaldi after only a short time using it.

Frankly the url bar, once i kill search suggestions, is the one thing that Mozilla has gotten right in recent years.

Type something in it, and it will do a sweep of history and bookmarks, trying to match the entered string within both url and page title.

Chromium derived browsers limit themselves to macthing the url, and only as if you are typing it as new.

Firefox definitely does it.

The behavior I described above happened in Firefox ESR on Debian Stretch.

If it has been fixed in the newfangled Firefox I'd love to know. (Not sure how to install Nightly on arm or I'd try it myself.)

Older Firefox versions (not sure if it is fixed or simply it no longer shows up on faster hardware) had an "interesting" race condition where if i hit enter and ctrl+t to spawn a new tab fast enough, the url would load in the new tab rather than the old.

Reply on news.ycombinator.com