Thanks — glad the Shift+2 example made the case. I'm keeping the default as it is, on purpose. If "unknown" meant "password", the program would fall silent in most Electron apps and web pages, where UI Automation answers slowly — it would stop doing its one job exactly where people type the most. Your worry about missed password fields was fair, though, and not only in theory. Up to 1.4.4 the program failed to recognise password fields in WinForms programs, and in Edge, Chrome and Firefox when you reached the field with Tab. That wasn't a timeout: the checks gave a wrong answer, so a fail-closed default wouldn't have caught it either. 1.5.0 fixes it — the program now listens to UI Automation focus events as well as asking EM_GETPASSWORDCHAR. And in a password field, Pause now only switches the layout; it never converts what was typed. What it keeps in ordinary fields stays in memory only: never written to disk, a log or a crash dump, and overwritten with zeros at every reset. If an app has its own password widget that slips past the checks, put the app on the exclusion list, and nothing typed there is kept at all.
