Re:Twitter for Mac is incapable of accepting certain letters...
by lilyball on Wednesday October 30, 2019 @05:17PM
(#21402847)
It's entirely possible where in Catalyst if a UIKeyCommand is registered that uses a non-modified letter, it overrides text input. Having said that, I can't imagine why Twitter for Mac would have solo-letter key commands registered during the login flow, and if they did then I can't imagine why they wouldn't also interfere during tweet composing. Or rather, I can imagine, but the scenarios I'm constructing would imply extremely contorted view controller hierarchies that make no sense.
[ Parent
| on HN ]
Re:Twitter for Mac is incapable of accepting certain letters...
by MikeBeas on Wednesday October 30, 2019 @05:26PM
(#21402950)
Can’t imagine why this would cause it to delete all input in the field when one of those characters is typed in using “reveal password” mode though. If you enable reveal, type in a string containing b, and then switch off reveal mode and add another character, it deletes the whole password. If it was just dropping inputs that would be one thing but this seems to be aggressively refusing to allow them in the field.
Re:Twitter for Mac is incapable of accepting certain letters...
by mackey on Wednesday October 30, 2019 @05:51PM
(#21403204)
It sounds like its specific to secure text fields, which I assume is why it doesn't interfere with tweeting. But thats a fair question about setting those up before login. My guess is those registrations aren't happening at the login VC level, or maybe in some global container VC. But I don't think that matters too much, because there are certainly use cases where you might want to show a secure text field even when logged in and you want shortcuts registered.