Bug 54037

Summary: "Close current tab" toolbar button doesn't activate when new tab openned in background
Product: [Applications] konqueror Reporter: wjl
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandrake RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description wjl 2003-02-03 23:05:29 UTC
Version:           3.1.0 (using KDE KDE 3.1)
Installed from:    Mandrake RPMsMandrake Linux Cooker i586 - Cooker
Compiler:          gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk)
OS:          Linux (i686) release 2.4.19-16mdksmp

The "close current tab" toolbar button doesn't active when a new tab is openned in the background.

To reproduce:

1) Add the "close current tab" button to an active toolbar in konqueror.

2) Change your konqueror settings so that "open links in a new tab instead of a new window" is selected.

3) Change your konqueror settings so that "automatically active new opened tabs" is *NOT* selected.

4) Make sure only a single tab is opened; at this point, "close current tab" should be disabled, because there is only one.

5) Middle click on a link; this makes a new tab but *doesn't active it* if you've set your settings properly. 

6) You now have two tabs, but the "close current tab" button isn't active.

7) If you switch the to the new tab, the toolbar button activates.

8) Switch back and forth all you want, it stays active.

9) Close one of the tabs, then middle-click on another link--the new tab appears, but the "close current tab" button again isn't active!

10) Repeat as often as you like, it doesn't get any less annoying. ;)

Note that this DOES NOT happen if "automatically activate new opened tabs" is selected. This probably means that some signal is sent when a new tab is *activated* which turns on the "close current tab" toolbar button. This signal instead should be sent when the new tab is *created*.
Comment 1 wjl 2003-05-17 07:59:42 UTC
This bug still exists in 3.1.1a 
Comment 2 Maksim Orlovich 2003-05-17 16:50:02 UTC
I fixed this in HEAD (future 3.2) a few days ago (noticed an another report, 
though). Will try backport in time for 3.1.3 
 

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