Summary: | tabbox should not initially adjust the focus chain, if the currently active client is not in the focus chain | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Cade <ahx2323> |
Component: | tabbox | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Flags: | thomas.luebking:
ReviewRequest+
|
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 5 | ||
Platform: | Mint (Ubuntu based) | ||
OS: | Linux | ||
URL: | https://git.reviewboard.kde.org/r/121024/ | ||
Latest Commit: | http://commits.kde.org/kwin/7747a38189e75659b195150900865b693c04aab1 | Version Fixed In: | |
Sentry Crash Report: |
Description
Cade
2014-11-03 09:09:13 UTC
That's because konsole is not in the focus chain - the present behavior (technically) actually makes sense. Activating konsole (which is not in the focus chain) does NOT impact the focus chain - kwrite is still on the top of this chain. With the next tabbox invocation, the focus chain is proceeded, moving chrome on top in this case. => the focus chain should not proceed if the currently active client is not in the focus chain Git commit 7747a38189e75659b195150900865b693c04aab1 by Thomas Lübking. Committed on 06/11/2014 at 21:58. Pushed by luebking into branch 'master'. step into the focus chain at the beginning if the index is 0, we close the circle, but if the index is -1 (invalid) we're "somewhere" and step into the focus chain - reasonably at the beginning REVIEW: 121024 M +4 -1 focuschain.cpp http://commits.kde.org/kwin/7747a38189e75659b195150900865b693c04aab1 |