search

keepassium / KeePassium

KeePass-compatible password manager for iOS
https://keepassium.com
Other
1.21k stars 103 forks source link

Cannot name new entries on macOS #205

Closed ghost closed 2 years ago

ghost commented 3 years ago

Description When creating a new entry on macOS, it is hard to name the entry. The field cannot be edited at first, but

How to reproduce Steps to reproduce the behavior (as seen in attached GIF):

  1. Click on create new entry
  2. Name entry.. upon failure enter username
  3. With luck, rename entry at this point.
  4. Otherwise, save the entry and reopen to rename

Expected behavior Create a new entry and name it.

Screenshots failure naming an entry

Environment: Using MacOS 12.0.1 and Keepassium macOS beta 1.28.97

.

keepassium commented 3 years ago

Thanks! Ironically, that field is supposed to get focused by default when the dialog opens. I wonder if mouse cursor's hovering nearby has any effect on the focus.

Overall, this seems to be a Monterey thing: I cannot reproduce this on 11.6. I will update my spare machine and look into this.

keepassium commented 2 years ago

Hmm, interesting… I have just tested on 12.0.1 and got an exactly opposite behavior: the whole row got selected initially, but then input focus quickly switched to the input field. Mouse cursor did not affect this at all.

https://user-images.githubusercontent.com/38399598/143721974-7911fbbf-4320-4073-a1b9-279aeb6c1a27.mov

Will investigate further.

ghost commented 2 years ago

When following your method by using the down key to select new entry, I cannot replicate the behaviour of the input field being selected. Also won't work when pressing cmd + N.

ghost commented 2 years ago

Sadly still a bug in Release 1.30.101

keepassium commented 2 years ago

@fazzer4x , thanks! Have you tried this on macOS 12.1, by any chance? I suspect this is a Mac Catalyst issue, so macOS update might just magically resolve this…

ghost commented 2 years ago

I am on 12.1 atm. The issue seems fixed on 1.30.102. I cannot replicate the erroneous behaviour anymore.

keepassium commented 2 years ago

Thanks! On my side, 1.30.101→1.30.102 did not change anything remotely related to this. So I guess the solution should be attributed to 12.0.1 → 12.1 instead :)