SUMMARY
Hey there,

I use KDE Plasma on my Notebook that I connect to USB docks with multiple displays attached regularly. When I wake my notebook from sleep, it has to redetect the displays (which is fine), but in this process, it's impossible for me to unlock my screen using a password. The issue is that when a new display is connected, the input focus switches from one display to another and since the password fields aren't synced across displays, I enter half my password on one screen and half my display on another. Sometimes it also seems that keys are registered multiple times when a new display is recognized while entering the password.
This is really annoying as I have to wait up to 30 seconds until all displays are correctly identified and configured, until I can unlock my screen.

STEPS TO REPRODUCE
0. set long password
1. Lock screen with no external display connected
2. (maybe let notebook go to sleep? Should not be relevant)
3. connect external display
4. try to enter password while display is being recognized
5. observe

OBSERVED RESULT
Password parts are entered on different screens, sometimes keys are registered multiple times and it's impossible to unlock the screen using a password

EXPECTED RESULT
I can enter the password and unlock the screen while external displays are recognized/configured

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0

ADDITIONAL INFORMATION
I see two possible solutions:
a) keep the input focus on one screen during password input when other displays are connected
b) sync the password across screens, so it doesn't matter if the focus switches
The second solution might be more tricky as I don't knwo what happens when the focus switches while keys are pressed. But in general: Why can I enter different passwords on different screens anyway? Why would I want to do that?
If helpful, I can attach a video showing the issue, but it should hopefully be fairly easy to reproduce :)