mirror of
https://github.com/brl/mutter.git
synced 2024-11-28 02:50:41 -05:00
6d8293a422
As per commit f71151a5 we focus an input window if no take-focus-window accepts
it. This might lead to an infinite loop if there are various focusable but
non-input windows in the stack.
When the current focus window is unmanaging and we're trying to focus a
WM_TAKE_FOCUS window, we intent to give the focus to the first focusable input
window in the stack.
However, if an application (such as the Java ones) only uses non-input
WM_TAKE_FOCUS windows, are not requesting these ones to get the focus. This
might lead to a state where no window is focused, or a wrong one is.
So, instead of only focus the first eventually input window available, try to
request to all the take-focus windows that are in the stack between the
destroyed one and the first input one to acquire the input focus.
Use a queue to keep track of those windows, that is passed around stealing
ownership, while we protect for unmanaged queued windows.
Also, reduce the default timeout value, as the previous one might lead to an
excessive long wait.
Added metatests verifying these situations.
Closes: https://gitlab.gnome.org/GNOME/mutter/issues/660
https://gitlab.gnome.org/GNOME/mutter/merge_requests/669
44 lines
540 B
Plaintext
44 lines
540 B
Plaintext
new_client 0 x11
|
|
create 0/1
|
|
show 0/1
|
|
|
|
new_client 1 x11
|
|
create 1/1
|
|
show 1/1
|
|
|
|
create 1/2 csd
|
|
set_parent 1/2 1
|
|
accept_focus 1/2 false
|
|
show 1/2
|
|
|
|
create 1/3 csd
|
|
set_parent 1/3 2
|
|
accept_focus 1/3 false
|
|
show 1/3
|
|
|
|
create 1/4 csd
|
|
set_parent 1/4 3
|
|
accept_focus 1/4 false
|
|
show 1/4
|
|
|
|
create 1/5 csd
|
|
set_parent 1/5 3
|
|
show 1/5
|
|
|
|
wait
|
|
assert_focused 1/5
|
|
assert_stacking 0/1 1/1 1/2 1/3 1/4 1/5
|
|
|
|
destroy 1/5
|
|
dispatch
|
|
|
|
assert_focused none
|
|
assert_stacking 0/1 1/1 1/2 1/3 1/4
|
|
|
|
destroy 1/2
|
|
dispatch
|
|
|
|
sleep 450
|
|
assert_focused 1/1
|
|
assert_stacking 0/1 1/1 1/3 1/4
|