Bug 65022

Summary:	After autocomplete disappears, focus is on wrong window
Product:	[Unmaintained] kdelibs	Reporter:	ewan dunbar <ewan.dunbar>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description ewan dunbar 2003-09-27 05:34:31 UTC

Version:            (using KDE KDE 3.1.1)
Installed from:    Compiled From Sources
Compiler:          gcc 2.95.3 20010315 
OS:          Linux

If the window manager is in mouse focus (not click) mode, and a combobox does an autocomplete, after the user selects a completion, or continues typing til no known completions are possible, the focus goes to the window under the mouse. It should go to the window containing the combobox.

Test case:
in a mouse focus mode, open a window that fills the screen. use a keyboard shortcut to bring up the Run Command dialog, with the mouse out of the area the dialog will appear in. type any letter which also begins a previously used command. when the autocomplete appears, do anything to make it disappear. focus will be on the big window, forcing the user to alt-tab back, and probably messing up whatever the user was doing in the big window by sending several (or many) keypresses to it if they don't notice in time.

Comment 1 Tobias Koenig 2003-11-02 13:13:05 UTC

Hi,

tested it with current CVS HEAD and can't reproduce this behaviour.
When I follow the instructions and open the 'Run Command' dialog, I can type in 'k'
and 4 apps from the history will be presented for autocompletion.
When I press escape now or type the full name of one app, the 'Run Command' dialog still has the focus and not the big window in the background (where the cursor is located).

Comment 2 ewan dunbar 2003-11-03 09:36:07 UTC

Subject: Re:  After autocomplete disappears, focus is on wrong window

I did not notice before -
the pointer must be over the area where the dropdown list of autocompletion 
candidates is to appear, but not inside the area where the 'Run Command' 
dialog will appear, for this to occur.

That is, if the dropdown list appears and extends beyond the bottom of the 
'Run Command' dialog, and the pointer happens to be in the area covered by 
the dropdown list, when escape is pressed or the full name of a completion is 
typed, the big window in the background has the focus.

(kde 3.1.1)

On Sunday 02 November 2003 07:13, Tobias "K

Comment 3 ewan dunbar 2003-12-07 05:54:01 UTC

Still happens in 3.2-beta1; behaviour of autocomplete has changed such that
it can only happen if the user hits escape. I also followed up earlier noting that
this bug only shows up if before the Run Command window is called up the cursor
is in an area where the dropdown box will fall.



New test case:

find a letter which, when typed into the Run Command dialog, will cause the
dropdown box to extend outside the dialog.

find the area outside the dialog where the dropdown box will extend.

in a mouse focus mode, open a window that fills the screen. use a keyboard
shortcut to bring up the Run Command dialog, with the pointer in the area outside
the dialog where the dropdown box will be. type an appropriate letter.

when the autocomplete appears, hit escape. focus will be on the big window.

Comment 4 Lubos Lunak 2004-11-19 19:15:01 UTC


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