https://bugs.kde.org/show_bug.cgi?id=500223
--- Comment #6 from John <ilikef...@waterisgone.com> --- (In reply to cwo from comment #5) > (In reply to John from comment #3) > > Once a field gets focus level 2, which is used for typing, then no matter if > > the user continues co move the mouse or press the up and down keys of the > > keyboard, the field that has focus 2 level should continue to be focused for > > input. > > FWIW, I disagree on this - if the user presses the up or down keys, it > should move to the previous or next items. That's what those arrow keys do, > and the user pressing them is in my opinion a clear statement that they want > this to happen. Having it be modal in the way you suggest would only make > sense to me if it would actually open a separate dialog-type interface, > where pressing escape to close is natural. Otherwise, escape should close > the primary dialog (i.e. the networks popup) I think I'm not that good at explaining things. I agree that if the user presses the up / down keys after selecting a network and clicking / pressing Enter (to enter its password), the selection focus (highlighted rectangle) should move. What I'm trying to say is that unless the user also clicks or presses enter on some other network, that was highlighted with its up / down key presses, the first network that has the click or the Enter pressed and its password field input opened (so it's now in a waiting for password state) should still get all the typed characters as there's none other network in a waiting for the password to be typed state. I just deleted my saved network (which I will call "My-network") to do a test (as if it were the first time) like this: 1. Opened the networks widget and moved the in the network list until "My-network" was selected. 2. Pressed Enter which showed the 'Password' input field, which became clearly focused as there was the blinking cursor waiting to type the password of the network. 3. Didn't type anything and pressed 'Down arrow' which moved the selection to the next network below. 4. Tried to type the password for "My-network" even though I was not there anymore (but one network down), though the password input field for "My-network" was still open and should have still received whatever I typed. The typed characters were not going anywhere else anyway, so they were just ignored. So the test failed! Going back up one network, by pressing the "Up" arrow, so exactly on "My-network" also failed to regain focus and let me type the password! Pressing Enter while exactly on "My-network" also failed to regain focus and let me type the password! I also closed the networks widget and did another test like this: 1. Opened the networks widget and moved the in the network list until "My-network" was selected. 2. Pressed Enter. 3. Pressed the "Down" arrow key to be on the next network. 4. Pressed Enter. 5. Pressed the "Down" arrow key to be on the next network. 6. Pressed Enter. This show another strange thing with multiple password input fields being shown, which in theory with only mouse hovering and focus could've work, but with keyboard navigation only one password field show by shown after Enter was pressed and that should have focus for input. If the user continues to press up or down arrows then the selection / highlight rectangle should of course move up or down as the user requested but when it presses Enter, then any previous password input field should disappear losing its focus of course and the new one should be opened gaining focus. I'm not sure I've explained it better this time, but a few quick test should reveal the problem(s) and hopefully what it should be done. -- You are receiving this mail because: You are watching all bug changes.
