You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, currently one has to choose each secret explicitly and then tap a corresponding button to push the respective token via USB or Bluetooth. Along with that, sensitive information is also displayed at the very first tab (including username and other login details), which is not nice if somebody looking at your screen. I would propose:
Display shortcut buttons to push token already in the list of secrets (for each of them);
Display sensitive login information only on the second tab if secret is chosen, and only buttons on the first tab.
The text was updated successfully, but these errors were encountered:
I also noticed one bug related to a keyboard button shortcut to the right of each record. As I understood with a long press it kind of tries to do what I proposed above, but unfortunately it:
types wrong characters, i.e. really the resulting typed password is a little bit incorrect compared to the one being typed when explicitly going into the record and tapping "password" button (so there is inconsistency for whatever reason);
it does not obey the setting to type Return after password, i.e. simply ignores it for whatever reason.
Hi @Alexander-Shukaev
thanks for the issue. Yes, indeed: the keyboard-icon is a shortcut to enter just the password. I just checked the source and yes, the default auto-type language is currently ignored by this functionaltiy, and Apple DE is hard coded for whatever reason. I have to fix it.
I also dont like the current TreeView much, e.g. due to only one shortcut button. But I did not find a better UI so far.
And from a UX perspective: you would expect that the shortcut button will follow the Return setting for this entry? I guess this would make sense as then it is consistent in the behavior.
Hi, currently one has to choose each secret explicitly and then tap a corresponding button to push the respective token via USB or Bluetooth. Along with that, sensitive information is also displayed at the very first tab (including username and other login details), which is not nice if somebody looking at your screen. I would propose:
The text was updated successfully, but these errors were encountered: