Bug 188587 - Middle-clicking too close to last opened tab in tab bar will cause new tab to be opened then immediately closed
Summary: Middle-clicking too close to last opened tab in tab bar will cause new tab to...
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: tabbing (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-01 10:07 UTC by peaches
Modified: 2009-10-22 20:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description peaches 2009-04-01 10:07:55 UTC
Version:            (using Devel)
Installed from:    Compiled sources

It looks like the tab bar will open new tabs on middle-click on MOUSE DOWN event, and close tabs on middle-click on MOUSE UP event, when middle-click is set up to do these.

So if you position the mouse on the tab bar to the right of the last opened tab, in the space where the new tab will appear and take up space, you're actually able to do a full middle click (down/up) where konqueror will create the new tab, then immediately close it, all from the single middle-click action. This is quick enough on my system to happen when clicking as fast as possible as long as the mouse is over the new tab's icon area, or click with a slight delay over the new title area. This behavior always occurs with a full tab bar cause middle-clickable tab area is so small.

KDE4 trunk r944788
Comment 1 Frank Reininghaus 2009-09-19 11:01:21 UTC
Confirmed in KDE 4.3.1 and current trunk (if a URL is in the clipboard, such that middle clicking the empty area in the tab bar will open a new tab with that URL).
Comment 2 Friedrich W. H. Kossebau 2009-10-22 20:27:08 UTC
SVN commit 1039099 by kossebau:

changed: emit signal mouseMiddleClick() on release, not press of the mouse button

Matches behaviour of the signals "mouseMiddleClick( QWidget* )" and, from KTabBar, "mouseMiddleClick( int )", which the former is based on

See http://reviewboard.kde.org/r/1923/
BUG:188587


 M  +9 -2      ktabwidget.cpp  
 M  +1 -0      ktabwidget.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1039099
Comment 3 Friedrich W. H. Kossebau 2009-10-22 20:43:22 UTC
Also backported to 4.3, so fix should be in 4.3.3