Bug 130760 - "Configure - Konversation" dialog cursor key menu tree navigation jumps back to the first group (Appearance)
Summary: "Configure - Konversation" dialog cursor key menu tree navigation jumps back ...
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-13 11:32 UTC by Robert Moore
Modified: 2006-07-14 03:16 UTC (History)
0 users

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 Robert Moore 2006-07-13 11:32:57 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Ubuntu Packages
OS:                Linux

This issue forces use of the mouse and so weakens Konversation's accessibility.

When using the keyboard alone, navigation of the Configure dialog in Konversation is restricted because the down cursor does not navigate to the next nested list in the tree view on the left on the window. If the mouse is used to select a nested item in the second (or any other than the first) nested list, cursor navigation jumps back to the top of the first nested list rather than continuing in the next open nested list.

Because top items Appearance, Behaviour and Notifications cannot be selected (clicking on them toggles nested lists to be toggled to shown or hidden), it is first necessary (with the mouse) to toggle the sublist to be shown, then (with the mouse) to switch the highlight list item to be able to use the keyboard to navigate. But, every time with the keyboard cursors, navigation down from the last item in a list jumps the focus to the top sublist, Appearance.
Comment 1 Eike Hein 2006-07-13 14:14:48 UTC
Confirmed. Note: Kate has the same problem.
Comment 2 Robert Moore 2006-07-13 20:36:57 UTC
Should this bug be reassigned to the kparts or kdelibs people?
Comment 3 Eike Hein 2006-07-13 20:38:57 UTC
I'd say it's a kdelibs problem. We could probably work around it with evil hacks, but shouldn't have to. 
Comment 4 Robert Moore 2006-07-13 23:34:06 UTC
Misassigned to Konversation Developers, as it's not specific to Konversation.
Comment 5 illogic-al 2006-07-14 03:16:56 UTC
would probably be best to reassign this as INVALID then.

On Jul 13, 2006, at 5:34 PM, Robert Moore wrote:

[bugs.kde.org quoted mail]