Bug 207789 - order in which dolphin parts are activated by tab key alterable?
Summary: order in which dolphin parts are activated by tab key alterable?
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
: 267572 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-09-18 14:12 UTC by Janet
Modified: 2021-07-29 21:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janet 2009-09-18 14:12:19 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I have a little problem with the order in which the dolphin parts are activated with the tab key and would appreciate a way to change it.

When dolphin is started, the filter bar is active (frame around it). The further tab key cycle here is:

nothing
places sidebar (no indicator that it is active!)
nepomuk search bar 
nepomuk search "enter" key
places sidebar tab
nothing
inside of folder
status bar: minus
status bar: slider
status bar: plus
nothing 
filter bar

This way just seems weird to me.

And sometimes I can use the arrow keys to switch to the next/previous part, sometimes only to go forward but not backwards.

What I would expect is that the inside of the folder or the places sidebar is active when I start dolphin (and the places sidebar should show an indicator when it is activated, like for the inside of the folder a small line under the first item). 

The order which I'd expect is:
places sidebar - places tab - inside of folder - filter - if window is split: inside of folder on the other side - status bar slider - search bar (last because it doesn't affect the current shown folder but the whole scenery) 

There is no need to separately activate the plus and minus sign in the status bar because they switch to the slider when you use them just with the keyboard. There also is no need to separately activate the search enter button when you use the keyboard because hitting enter starts the search. 

When the places sidebar tab is activated using the up arrow should activate the current sidebar content.

When I click on the places sidebar tab with the mouse it should get the focus so I can switch tabs with the arrow keys. Instead the previous activated elements stays active, e.g. the folder content.

When I can navigate in the places sidebar content and click onto the folder tab to change to the folder view I cannot instantly use the arrow keys for the tree, I first have to activate it with a mouse click onto one folder in the tree. I cannot activate it instantly with the keyboard without going through the whole cycle.

This leads me to:

1. Mouse and keyboard activation of the parts shouldn't be independent from each other. When I activate an element with the mouse I should be able to use it with the keyboard as if I had activated it with the tab cycle.

2. There shouldn't be obviously unnecessary parts in th- folder tabs.e tab cycle.

3. There shouldn't be "empty" elements in the cycle: when something is not shown (e.g. the filter bar) it should fall out of the tab cycle. Every tab in the cycle should do something, no blanks.

4. The cycle should begin near the content because using the content is one main reason to open the filemanager. By now I need 7 tab key steps to access the content after opening a dolphin window.

5. The sidebar content should be activatable from the sidebar tabs with the up arrow key. By now you either have to use the mouse or use the tab key 9 times or Shift-Tab 3 times.
Comment 1 Peter Penz 2009-09-18 16:19:39 UTC
Yes, the tab handling is still a mess... I wanted to solve this already a long time ago.
Comment 2 Nick Shaforostoff 2012-02-22 17:33:16 UTC
*** Bug 267572 has been marked as a duplicate of this bug. ***
Comment 3 Nick Shaforostoff 2012-02-22 17:34:25 UTC
as a user I expect that in SplitView mode Tab key is used for moving
focus between views, like in Midnight Commander
Comment 4 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:52 UTC
Resetting assignee to default as per bug #305719
Comment 5 Justin Zobel 2021-03-09 02:18:47 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 6 Prajna Sariputra 2021-07-29 21:52:16 UTC
I can confirm that this is still an issue with 21.04.3, as the amount of tabbing needed still changes depending on whether the tab bar exists for example, and having a different tab open also changes it yet again.