Lost Inputs 0 ▲ Kevin Cox's Blog 3 hours ago · Tech · hide · 0 comments A UI shouldn’t lose your inputs.If you are typing, each and every key should result in a letter in order. No characters should e mssig or rerodeerd.If I switch windows with Alt+Tab and then type, the events must always go to the newly focused window.If I close a tab with Ctrl+w and then type, the events must go to the newly focused tab.This may seem obvious, but I often see applications that behave incorrectly if your inputs come too fast. One common situation where I see interfaces falter is keyboard shortcuts that bring you to a text input. Keypresses after the shortcut should always land in that input.ExamplesApp LaunchersA common example is an app launcher. On GNOME I tap Super and type to search my apps. If I type Superfoo it should search for “foo” every time. GNOME works correctly here. No matter how overloaded and laggy my system is, and no matter how fast I type, the search is accurately captured. KDE’s KRunner does not pass this test. Oftentimes the first few characters of… No comments yet. Log in to reply on the Fediverse. Comments will appear here.