Bug 62208

Summary:	disabled autoraise ignored by fullscreen applications when focus follows mouse
Product:	[Plasma] kwin	Reporter:	Elmar Loos <elInfo>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Elmar Loos 2003-08-05 21:33:22 UTC

Version:           v1.9.8 (using KDE 3.1.3)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3.1 20030722 (Debian prerelease)
OS:          Linux (i686) release 2.4.20

Tested with: 
- Konsole
- konqueror

Settings: 
- Focus follows mouse
- Autoraise disabled
- Click raise enabled

Reprodution: 
- make application running in fullscreen mode
- use Alt-Tab to raise a smaller window 
- move mouse to the fullscreen application

Expected behavior:
- the fullscreen application gets focus but stay lower (does not raise)

Actual behavior:
- the fullscreen application gets focus and is raised to top

Comment 1 Wojciech Jarosz 2003-12-08 20:16:19 UTC

Similar behavior happens when using gwenview to view images in fullscreen. If you use Focus Follows Mouse (no auto raise, and no click raise), then switching in and out of fullscreen makes the whole screen flicker as if the focus is being fought over my two apps. I do not even have to use alt-tab to create this situation. The only way I have figured out how to make this stop is by moving the cursor to the area of the screen where kicker is. Also happens with konsole and konq.

Reproduction:
- switch to fullscreen view in any one of konq, konsole, or gwenview.

Comment 2 Wojciech Jarosz 2003-12-08 20:24:27 UTC

I should also add: If switching application A to fullscreen, flicking happens only if some other application B is also under the cursor (below application A). If the only thing under the cursor is application A and the desktop, then flicking does not happen.

Comment 3 Lubos Lunak 2003-12-09 15:51:03 UTC

This should be fixed already.

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

Comment 4 Lubos Lunak 2004-01-16 17:39:49 UTC

The original issue is actually not fixed yet.

Comment 5 Lubos Lunak 2004-01-19 16:15:44 UTC

Should be fixed now.