summaryrefslogtreecommitdiff
path: root/www-client/chromium/files
diff options
context:
space:
mode:
authorV3n3RiX <venerix@koprulu.sector>2021-10-30 19:43:03 +0100
committerV3n3RiX <venerix@koprulu.sector>2021-10-30 19:43:03 +0100
commit162945d2a91899b637bbb9e163b406350de12906 (patch)
tree49cc2cc66f724a7c6f033f93aaba4ae3be1f2259 /www-client/chromium/files
parentf660c6de84558324d784218831d8f0782ee41e2e (diff)
gentoo resync : 30.10.2021
Diffstat (limited to 'www-client/chromium/files')
-rw-r--r--www-client/chromium/files/chromium-95-xfce-maximize.patch30
1 files changed, 30 insertions, 0 deletions
diff --git a/www-client/chromium/files/chromium-95-xfce-maximize.patch b/www-client/chromium/files/chromium-95-xfce-maximize.patch
new file mode 100644
index 000000000000..296d97873ddc
--- /dev/null
+++ b/www-client/chromium/files/chromium-95-xfce-maximize.patch
@@ -0,0 +1,30 @@
+From 603d765ca5154db27718d89a2ee9be2a95a64254 Mon Sep 17 00:00:00 2001
+From: Alexander Dunaev <adunaev@igalia.com>
+Date: Fri, 29 Oct 2021 20:54:46 +0700
+Subject: [PATCH] [linux/xfce] Set zero insets on maximising the window.
+
+It turned out that Xfwm handles the frame insets not the way KWin and
+Mutter do.
+
+Bug: 1260821
+Change-Id: I69e71049157c03b74d78bc5edb7a60bf39cdda8b
+---
+
+diff --git a/ui/platform_window/x11/x11_window.cc b/ui/platform_window/x11/x11_window.cc
+index dd381747..706f19c 100644
+--- a/ui/platform_window/x11/x11_window.cc
++++ b/ui/platform_window/x11/x11_window.cc
+@@ -676,6 +676,13 @@
+ // save this one for later too.
+ should_maximize_after_map_ = !window_mapped_in_client_;
+
++ // Some WMs keep respecting the frame extents even if the window is maximised.
++ // Remove the insets when maximising. The extents will be set again when the
++ // window is restored to normal state.
++ // See https://crbug.com/1260821
++ if (CanSetDecorationInsets())
++ SetDecorationInsets(nullptr);
++
+ SetWMSpecState(true, x11::GetAtom("_NET_WM_STATE_MAXIMIZED_VERT"),
+ x11::GetAtom("_NET_WM_STATE_MAXIMIZED_HORZ"));
+ }