| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We refuse to move focus while a grab operation is in place. While this
generally makes sense, there's no reason why the window that owns the
grab shouldn't be given the regular input focus as well - we pretty
much assume that the grab window is also the focus window anyway.
In fact there's a strong reason for allowing the focus change here:
If the grab window isn't the focus window, it probably has a modal
transient that is focused instead, and a likely reason for the focus
request is that the transient is being unmanaged and we must move
the focus elsewhere.
https://gitlab.gnome.org/GNOME/mutter/issues/15
|
|
|
|
|
|
|
|
| |
It doesn't make much sense to globally unset focus when mapping
a new window.
Based on mutter commit:
https://gitlab.gnome.org/GNOME/mutter/-/commit/998d921d418a7e943ea
|
|
|
|
| |
FOCUSED_WINDOW layer does not exist.
|
|
|
|
|
|
| |
This reverts commit 12c4f35ca5a6f596518d50b2b2c647608c3d3410.
https://gitlab.gnome.org/GNOME/metacity/issues/8
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Timeouts are not used since de65967b62d46d6dd01352d5fb5104f88f30d88e.
|
|
|
|
|
|
|
|
|
| |
Changes to remove frame for fullscreen windows have introduced
regression - Firefox will cancel fullscreen if it receives focus
out event before _NET_WM_STATE property change event.
Use idle to ensure or destroy frame after window features are
recalculated and window state set.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is attempt to fix/silence coverity overlapping assignment
issues - CID 1491451 and CID 1491452.
In practice this does not seem to change anything, in both cases
clang and gcc generates same assembly output with optimization
level 1 or higher.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
And do not fill surface with opaque black (the default source
pattern).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In addition to existing properties use also new _GNOME_WM_STRUT_AREA
property that allows creating struts between monitors.
https://mail.gnome.org/archives/wm-spec-list/2018-December/msg00000.html
https://gitlab.freedesktop.org/xdg/xdg-specs/merge_requests/22
|
|
|
|
|
|
|
|
|
|
|
| |
In addition to existing _NET_WORKAREA property set also new
_GTK_WORKAREAS_Dn property where n is desktop number (between 0
and _NET_NUMBER_OF_DESKTOPS - 1).
https://mail.gnome.org/archives/wm-spec-list/2018-December/msg00000.html
https://gitlab.freedesktop.org/xdg/xdg-specs/merge_requests/22
https://gitlab.gnome.org/GNOME/metacity/merge_requests/3
|
|
|
|
| |
https://gitlab.gnome.org/GNOME/mutter/commit/c13ea4f48ddbb8dfe67acc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When window that is direct child of root window and have input
focus with revert_to set to RevertToParent closes focus will revert
to root window. This used to be problem when metacity did not
manage override redirect windows.
Now fix in commit 714fb3d539cdaf7fafe6205d114e6a29276bd7b7 is
obsolete as metacity these days have MetaWindow also for override
redirect windows, meaning that focus will be moved to another
window when any focused window will close.
Also debug message is misleading, it has nothing to do with
gnome-session. For example closing any client side decorated GTK
window will log this debug message and may move focus to wrong
window as we no longer have not_this_one window.
Original bug:
https://bugzilla.gnome.org/show_bug.cgi?id=153220
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit f628d8f8901f46fa9e00707ae9d7ccfd1e85f427 changed how we
choose the default focus window from the MRU to the topmost in the
stack. Unfortunately most of the time this gives unexpected result
if there are windows in META_LAYER_TOP and/or META_LAYER_FULLSCREEN
layers.
Re-sort windows using only stack position with one exception, keep
windows in META_LAYER_DESKTOP layer last and apply two rules when
choosing default window:
- fullscreen window should not get focus if it is not on the same
monitor as not_this_one window. If fullscreen window is on other
monitor then windows under it also should not get focus.
- desktop window should be always last choice.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GTK+ doesn't support shading of client-side decorated windows, and likely
never will (not least because shading is conceptually questionable if the
app customizes the titlebar), and neither do other CSD implementations like
Chromium's. A shortcut that only works with a decreasing number of windows
is more confusing than helpful, so don't expose it.
https://bugzilla.gnome.org/show_bug.cgi?id=645460
From mutter:
https://gitlab.gnome.org/GNOME/mutter/commit/32547d2eff23bcbfed58ed
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 33a6a39c9a7f1a0d706d79175c7ed157984f3da0.
Original commit was:
https://gitlab.gnome.org/GNOME/mutter/commit/b3b9d9e1617f350a2a3f3a
Commit in metacity was incomplete and because of that also did not
reflect what it actually did. Also exactly this part was reverted in
mutter - https://gitlab.gnome.org/GNOME/mutter/commit/d99442d6e6b7.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|