Bug 381269

Summary: Switching tabs with keyboard
Product: [Applications] dolphin Reporter: Magnus Johansson <johanssongreppet>
Component: panels: foldersAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: elvis.angelaccio, nate, simonandric5
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:

Description Magnus Johansson 2017-06-16 07:37:16 UTC
When switching tabs in Dolphin with Ctrl+Tab the focus shifts away from the list of folders to the tab row. I think the focus should stay in the list of folders so one directly can navigate among the folders in the new tab with e.g letter keys. Now, one has to press Shift+Tab three times in order to get the focus in the list of folders in the new tab after switching to it with Ctrl+Tab or Alt+underlined letter.
Comment 1 Nate Graham 2017-06-16 17:11:31 UTC
I see you're using Debian stable, which has older versions of Plasma and Dolphin. I can't reproduce this in Kubuntu 17.0.4, which has Plasma 5.9.4 and Dolphin 16.12.3 which are likely much newer than what you've got.

Debian 9 is about to come out, and it will include newer versions of this software. Would you mind seeing if the issue reproduces at that time?
Comment 2 Magnus Johansson 2017-06-16 17:48:31 UTC
Thanks for the information, Nate. Can't I update Plasma and Dolphin in Debian 8?
Comment 3 Nate Graham 2017-06-16 18:03:53 UTC
Generally no. Debian Stable's model is to lock packages and programs at known stable versions, with upgrades coming alongside new major releases of Debian itself. Lucky for you, Debian 9 is just around the corner. If you want to stick with Debian 8, you'll need to backport newer versions from Debian Testing or Sid, or else build them from source.
Comment 4 Magnus Johansson 2017-06-16 18:30:50 UTC
OK, thanks again. I shall see if the problem is still there when I get the opportunity to use Debian 9.
Comment 5 Elvis Angelaccio 2017-06-16 21:16:32 UTC
Yep, this was fixed a while ago.

*** This bug has been marked as a duplicate of bug 338892 ***