In the lock screen, pressing the enter key while the UI is not yet
visible ends up trying to unlock (and would usually fail because the
password field is empty).
Ensure that the UI is visible before unlocking.
BUG: 395671
ngraham | |
davidedmundson |
Plasma | |
VDG |
In the lock screen, pressing the enter key while the UI is not yet
visible ends up trying to unlock (and would usually fail because the
password field is empty).
Ensure that the UI is visible before unlocking.
BUG: 395671
Lock the session, press enter. The UI should appear without any
"Unlocking failed" message.
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
The new lock screen runs the risk of adding extra steps for the user. This is one change that can help the issue because IIRC in Windows you also have a double lock screen and pressing Enter will get you to the password prompt; I assume the users who have had experience with Windows would expect Plasma to do the same, hence the bug reports. I would also suggest to add something like a "Type to unlock..." text to the unblurred screen because it's not intuitive that the user can just start typing their password, and they should be saved from having to move their mouse etc.
EDIT: Submitted the latter as a feature request.
Could you create a feature request in https://bugs.kde.org/ about the "Type to unlock..." label ? That should be done in a separate patch, I believe.
Very clever way of solving the problem! I took a look myself a few days ago but got stuck. I like your solution. It works well and I couldn't find any regressions.
Please get a second opinion from a Plasma person before landing. Also, this could probably be considered a bugfix and landed on the stable branch.
It's ok as-is, there's a code change that would make things a bit better.
lookandfeel/contents/lockscreen/MainBlock.qml | ||
---|---|---|
66 | It's generally bad practice to reference properties in the parent scope, it makes future refactors very difficult. I would prefer an explicit property on MainBlock and then have LockScreenUi.qml bind that when it instantiates the MainBlock. |
Let's land this on the Plasma/5.14 branch and then merge to master. See https://community.kde.org/Infrastructure/Phabricator#Landing_on_the_.22Stable_branch.22