Bug 309765

Summary: Closing a tabbed window gives focus to an other, but doesn't raise that
Product: [Plasma] kwin Reporter: Unknown <null>
Component: window-tabbingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: normal Flags: thomas.luebking: ReviewRequest+
Priority: NOR    
Version: 4.9.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 4.10
Attachments: xwininfo and xprop of Okular and Opera

Description Unknown 2012-11-08 19:40:35 UTC
1.) Set automatic window tabbing
2.) Open a web browser (Opera or Firefox preferred, not Chrome) and open this link twice: http://www.theavaloneffect.com/TermsAndConditions.pdf (first Google hit)
3.) Now you have two Okulars opened with this PDF file. Close both of them with Ctrl+Q one after the other quickly.
4.) Navigate further.

Reproducible: Always

Actual Results:  
After the first document closed, the web browser will close, because that got the focus.

Expected Results:  
Either the browser should be raised or the other document should be given the focus.
Comment 1 Thomas Lübking 2012-11-08 20:38:39 UTC
Can you attach the outputs of "xprop" and "xwininfo" for both, browser and okular?
Comment 2 Unknown 2012-11-08 20:58:30 UTC
Created attachment 75109 [details]
xwininfo and  xprop of Okular and Opera
Comment 3 Thomas Lübking 2012-11-08 21:28:59 UTC
Not what i had expected.
Anyway - the tabs should likely have highest precedence on closing a client, because on the frontend, no window has actually been closed.

https://git.reviewboard.kde.org/r/107258/
Comment 4 Thomas Lübking 2012-11-14 20:33:47 UTC
Git commit 7f513b9e286013486f422a7aac7b61f7d70265af by Thomas Lübking.
Committed on 08/11/2012 at 22:26.
Pushed by luebking into branch 'master'.

activateNextClient precedence for next client in tabgroup
FIXED-IN: 4.10
REVIEW: 107258

M  +11   -3    kwin/activation.cpp

http://commits.kde.org/kde-workspace/7f513b9e286013486f422a7aac7b61f7d70265af