Summary: | Closing a tabbed window gives focus to an other, but doesn't raise that | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Unknown <null> |
Component: | window-tabbing | Assignee: | 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: | http://commits.kde.org/kde-workspace/7f513b9e286013486f422a7aac7b61f7d70265af | Version Fixed In: | 4.10 |
Sentry Crash Report: | |||
Attachments: | xwininfo and xprop of Okular and Opera |
Description
Unknown
2012-11-08 19:40:35 UTC
Can you attach the outputs of "xprop" and "xwininfo" for both, browser and okular? Created attachment 75109 [details]
xwininfo and xprop of Okular and Opera
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/ 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 |