Bug 214292 - [REGRESSION] tab bar has focus after aborted tab drag
Summary: [REGRESSION] tab bar has focus after aborted tab drag
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-12 18:43 UTC by Matthew Woehlke
Modified: 2011-02-26 23:44 UTC (History)
0 users

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 Matthew Woehlke 2009-11-12 18:43:26 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

After an aborted tab drag, focus gets left on the tab bar. It should go to the pty.

To reproduce:
- Click on a tab; hold the mouse button like you are going to drag.
- Move mouse until tab starts dragging.
- Release tab so that its position does not change (either move it to the same place, or release somewhere invalid e.g. over the pty)
- Observe that the pty does not have focus.

The tab bar has focus at this point; an (unmodified) arrow key can change the tab, but changing the tab will correctly return focus to the pty.

4.3.2 does not show this behavior, visible in at least svn circa Nov. 2.
Comment 1 Christoph Feck 2009-11-16 22:49:23 UTC
It's worse. The tabbar also gets focus by simply clicking on it. I often activate the Konsole window by clicking on the tab, and its annoying to click into the window again to activate the cursor. I think there were some changes in KTabWidget/KTabBar recently.
Comment 2 Matthew Woehlke 2009-11-17 17:47:04 UTC
Hmm, you're right. I remember seeing that mentioned, but thought I wasn't seeing it. I think what happens is if you have changed tabs in any way (either switch to a new tab, or reorder tabs), then Konsole bounces the focus back as it should.

So is this a duplicate, or was there not an actual report previously? (I didn't find an existing report...)
Comment 3 Kurt Hindenburg 2011-02-26 23:44:09 UTC
I believe all these issues have been fixed in recent versions (4.5.x+)