https://bugs.kde.org/show_bug.cgi?id=500223
--- Comment #3 from John <ilikef...@waterisgone.com> --- (In reply to cwo from comment #2) > (In reply to John from comment #1) > > I made a similar bug report 3 years ago: > > https://bugs.kde.org/show_bug.cgi?id=454523 > > I think this is just the same issue (I can't see a meaningful difference) so > I'm marking this as a duplicate. > > In principle this should be trivial to fix, but with such cases where the > currentIndex is set on hover there's the chance of things breaking. I'll put > it on my todo list to investigate here. > > *** This bug has been marked as a duplicate of bug 454523 *** Well I think you're were right into making this a duplicate of the other bug (which I've set as confirmed now). Maybe also that's why nobody looked into it as it stayed only reported until now. As for the currentIndex, I have no idea as I have no experience with Qt or KDE software, just a bit with web development. But from what I've seen, web browser don't have such problem when they are multiple input input fields (text fields or not), like in a web form, but it's probably also because they don't do anything just on hover. I'm thinking that Qt or KDE Frameworks, if it's involved here, should have an option that when an input field is focused and not only focused by hover, but focused level 2, by being clicked or by pressing Enter (if the "hovering" was done by keyboard navigation) to not lose focus that is needed for input: Let me rephrase that, maybe it's easier to understand: Focus level 1, can be done by: -Hovering with the mouse -Up and down arrows of the keyboard Focus level 2, can be done by: -Clicking with the mouse -Pressing Enter with the keyboard 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. Until another field that is having focus level one by the mouse hover or keyboard up / down arrows gets a click or an Enter which turns that field in focus level 2. If no other field is getting a click or an Enter, but we still want to escape the focus level 2 of the first field, I think a click on the Desktop or pressing ESC on the keyboard should do it. I'm not sure if this is such a good logic, if it makes any sense or it's even possible with Qt and other already existing KDE software, but If I were a developer this is how I would try to fix it first. Thanks a lot for putting it on your TODO list, we appreciate it! -- You are receiving this mail because: You are watching all bug changes.
