Version: unspecified (using KDE 4.5.1) OS: Linux On several locations the Keyboard navigation isn't usable. If you rename things with F2 you cannot switch over to another Window and back and continue your work like anticipated. Reproducible: Always Steps to Reproduce: If you push F2 to copy a text, push enter to exit the rename field Alt+Tab away and Alt+Tab Back, than everything works fine. BUT if you don't push Enter before Tabbing away, you cant use the Keyboard right away if you Tab back. You than have to push several times tab, to continue your work. One of the many areas where Keyboard navigation is inconsistent!
Thanks for reporting this issue.
Not exactly the way i experience this. Your "BUT" case is true but you don't need to tab. If you do that you indeed have to tab several times because you cycle through a few widgets. But if you use the arrow up you will see that it works fine. However, and that is an issue, if you use other arrow keys you suddenly seem to be in the zoom widget. I guess there is a focusing issue here. Anyone else any ideas where this might go wrong?
I can't reproduce this with 4.6.3. Here when going back via Alt Tab one has to press F2 again. If you still have this problem then please reopen this report.
Ah, just noticed I have the same issue as descriped in comment #2
OK I once again tested this behaviour in KDE 4.7.3 on Ubuntu 11.10 and it is still the same. But to specify it a bit more I have to say that i have "inline Rename" activated and the expected active widget after tabbing back into the window should be the file list, but thats not the fact. I think here is in fact a focus problem.
I'm experiencing similar problems with dolphin from KDE 4.8.90 (Dolphin 2.0.95). After renaming a file and hitting return, the focus seems to be somewhere else, because I cannot navigate using up/down arrow keys, unless I press tab several times. Steps to reproduce: 1. select a file 2. press f2 3. press enter 4. try to navigate using arrow keys.
(In reply to comment #6) > I'm experiencing similar problems with dolphin from KDE 4.8.90 (Dolphin > 2.0.95). Your porblem is a bug introduced in reimplementing the inline renaming during the 4.9 cycle . Of course, it has been fixed in the final KDE SC 4.9.0 .
Resetting assignee to default as per bug #305719
[Part of the Dolphin Bug Weeks 2012] The orriginally reported bug still exists in Dolphin 2.1/KDE SC 4.9.2 (openSUSE 12.2.6 KR45 package).
Review-Request: https://git.reviewboard.kde.org/r/116119/
If I rename a file using F2 (with inline renaming on), as soon as I press ENTER to confirm the new name, all the files in that folder from the first to the renamed one are automatically selected (?!). Files listed after the one that was renamed are not selected. Is this related to the problem reported here or should I file another bug? I'm running Kubuntu 14.04 and KDE 4.13.0.
(In reply to comment #11) > If I rename a file using F2 (with inline renaming on), as soon as I press > ENTER to confirm the new name, all the files in that folder from the first > to the renamed one are automatically selected (?!). Files listed after the > one that was renamed are not selected. > Is this related to the problem reported here or should I file another bug? > I'm running Kubuntu 14.04 and KDE 4.13.0. Please open a new bug report. Thanks! (Hmm or maybe related to bug 329377?)
Wulf can you please confirm this is still an issue with the most recent version of Dolphin.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!