Bug 274456 - [GTK3] Snippet80 eats away navigation through keyboard
Summary: [GTK3] Snippet80 eats away navigation through keyboard
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-04-29 22:40 EDT by Praveen CLA
Modified: 2020-06-09 05:43 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Praveen CLA 2009-04-29 22:40:05 EDT
Build ID: I20090428-0100

Steps To Reproduce:
1. Launch snippet80 on GTK
2. We are not able to move the treeitem through keyboard - either through arrow keys or through the first alphabet character.
The problem is that code in the SelectionListener eats away the selection/navigation.


More information:
In Other platforms, I am able to move the tree item normally.
Comment 1 Bogdan Gheorghe CLA 2009-07-30 16:17:01 EDT
Praveen, this seems like a good one to look at.
Comment 2 Praveen CLA 2009-07-31 11:57:48 EDT
In GTK, when the elements are unselected, then cursor-focus remains on the last focused element. At this moment, if the elements are tried to navigate (through Up/Down arrow keys), then GTK considers the newly selected element as the same element instead of next/previous element in the tree.
In snippet80, initially 'Item0' has cursor-focus. An attempt to navigate down (through arrow key) to 'Item1' is not permitted because getSelection() in SelectionListener returns 'Item0'. Thus, the revised selection is empty and thus, elements are unselected again.
This appears to be the native behaviour of GTK that navigation stays on the same element when it has cursor-focus.
Comment 3 Eric Williams CLA 2016-11-24 17:24:16 EST
This is still reproducible.
Comment 4 Eclipse Genie CLA 2020-06-09 05:43:46 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.