Bug 170717 - Konqueror doesn't restore focus to KatePart when losing and regaining it
Summary: Konqueror doesn't restore focus to KatePart when losing and regaining it
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-09 07:06 UTC by Stephan Sokolow
Modified: 2009-06-20 19:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Sokolow 2008-09-09 07:06:22 UTC
Version:            (using KDE 3.5.9)
Installed from:    Compiled From Sources

When the active tab in a Konqueror window is displaying text/plain via KatePart and KatePart has keyboard focus, I expect that focus to be preserved when I change to a new window (eg. changing desktops or popping Yakuake open) and then restore focus to Konqueror (any way will work).

However, that is not what happens. Instead, the widget focus seems lost to the ether. No widget is visibly focused and Arrow/PageUp/PageDown keypresses have no effect. This is always irritating, because clicking to restore focus will also reposition the cursor, but it's especially bothersome when I'm trying to keep both hands on the keyboard.

As an interesting side-note, focus is NOT lost when switching tabs or when tab-switching occurs after the window regains focus. The problem only occurs when the window loses and regains focus without tab-switching.
Comment 1 Frank Reininghaus 2008-09-09 18:32:01 UTC
Thanks for the bug report. I'm unable to reproduce this on 3.5.10 and 4.1.1 (Kubuntu) - the text widget remains focused, and the cursor stays at the same position when I switch to another desktop and back.
Comment 2 Stephan Sokolow 2008-09-10 02:00:55 UTC
I'm on Gentoo, so I'll check whether the fixes are in vanilla 3.5.10 and 4.1.1 as soon as they become available via the Portage tree. (I don't have time to build a test setup manually)
Comment 3 Eduardo Robles Elvira 2009-06-20 19:51:22 UTC
Should work fine in any recent version KDE 4, and KDE 3 is not supported anymore so if you still have the problem in KDE 4 please reopen the bug.