Bug 158987

Summary: line edit widget loses focus on each tab-keypress when completion mode is set to "automatic"
Product: [Unmaintained] kdelibs Reporter: pada
Component: kdeuiAssignee: kdelibs bugs <kdelibs-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: jr, martin
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description pada 2008-03-09 01:41:51 UTC
Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc 4.2.3 
OS:                Linux

The filename input dialog combo-box loses focus when tab is pressed in "automatic" auto-completion mode.

How to reproduce:

1. Start konqueror or any other KDE application with a file open/save dialogue
2. Select "open" from the menu
3. Right click on the address/filename input combo-box and select autocompletion mode: automatic
   (expected behavior: filename completion is shown in a greyish colour and pressing tab autocompletes the input while keeping the focus in the combo-box to continue typing your path)
4. Enter /u
   -> expected behavior: shows "/u" in black and "sr" in grey, after pressing tab shows /usr and place cursor behind /usr
   -> observed behavios: shows "/u" in black and "sr" in grey, after pressing tab shows /usr, but combo-box loses focus and it is not possible to type path

Important: This can only be reproduced in completion mode "automatic" and this bug seems to apply not only to KDE 3.5.x, but also to KDE 4.x

Kind regards,
Daniel
Comment 1 Christoph Feck 2009-08-27 03:33:09 UTC
*** Bug 70768 has been marked as a duplicate of this bug. ***
Comment 2 Martin Koller 2012-09-08 20:18:05 UTC
Still the case in 4.9.1
Comment 3 Christoph Cullmann 2024-09-14 17:06:38 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have resolved this bug.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann