upd: 95.0.4638.69 -> 96.0.4664.45

.abf.yml

@@ -1,6 +1,6 @@
 sources:
-  chromium-95.0.4638.69.tar.xz: 155f2c409145cb1a8beb00ae536ccb234680da84
-  chromium-gost-93d62c39418a448be572d061dbd1d0c886ded2e0.tar.gz: 6b7ee2ad473353ee26a0f666d71b4d5a824c6a80
+  chromium-96.0.4664.45.tar.xz: e08bf22a86057183b3a7cfeaaf501f5d94ae29d6
+  chromium-gost-edfb3698025cb3a6a0355c8dd600764ea52925c1.tar.gz: 34acb1a361076e0bfe0b30ae2d987b1c74d68ffb
   depot_tools.tar.xz: 082b7f9a4dfa7eb03900755b4866aef2d73543a5
   icons.tar.bz2: a835954af164bf38f8ea4ea80608839bed7800a3
   msspi-1df40c96e1dfdc6bbe97c321aceae45114a89dd8.tar.gz: c2f9fb6ec24205ab39a58946b2acc72c54ab40a6

24a90f9327ac1a4d2b6dbb410cd28f65e3e33839.patch

@@ -1,40 +0,0 @@
-From 24a90f9327ac1a4d2b6dbb410cd28f65e3e33839 Mon Sep 17 00:00:00 2001
-From: Alexander Dunaev <adunaev@igalia.com>
-Date: Mon, 1 Nov 2021 19:29:27 +0000
-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, which causes wrong window size when it is maximised (see the
-linked crbug).
-
-This patch resets the frame insets to zero when the window is maximised,
-which fixes the behaviour on Xfwm.
-
-Bug: 1260821
-Change-Id: I69e71049157c03b74d78bc5edb7a60bf39cdda8b
-Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3250747
-Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
-Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
-Cr-Commit-Position: refs/heads/main@{#936990}
----
- ui/platform_window/x11/x11_window.cc | 7 +++++++
- 1 file changed, 7 insertions(+)
-
-diff --git a/ui/platform_window/x11/x11_window.cc b/ui/platform_window/x11/x11_window.cc
-index 017ff15a0af1b..dd416c031e7c1 100644
---- a/ui/platform_window/x11/x11_window.cc
-+++ b/ui/platform_window/x11/x11_window.cc
-@@ -675,6 +675,13 @@ void X11Window::Maximize() {
-   // 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"));
- }

chromium-browser-stable.spec

@@ -50,7 +50,7 @@
 # GOST patches and sources
 # Using commit hashes because upstream often puts tags long after making changes
 # (they wait for builds to finish to make a new "release" with binary packages)
-%define chromium_gost_commit 93d62c39418a448be572d061dbd1d0c886ded2e0
+%define chromium_gost_commit edfb3698025cb3a6a0355c8dd600764ea52925c1
 %define msspi_commit 1df40c96e1dfdc6bbe97c321aceae45114a89dd8
 %define _gostsourcedir %{_builddir}/chromium-gost
 
@@ -83,8 +83,8 @@
 
 Summary:	A fast web browser based on the Blink engine
 Name:		chromium-browser-stable
-Version:	95.0.4638.69
-Release:	7
+Version:	96.0.4664.45
+Release:	1
 License:	BSD, LGPL
 Group:		Networking/WWW
 Url:		https://www.chromium.org/Home
@@ -130,7 +130,6 @@ Patch649:	off-java-check.patch
 # https://gitlab.xfce.org/xfce/xfwm4/-/issues/603
 Patch651:	314a1e4d19141b60850fc542abab6251c4f119c9.patch
 Patch652:	245e71ae8de3f4b5f3478739be819981bb12dfab.patch
-Patch653:	24a90f9327ac1a4d2b6dbb410cd28f65e3e33839.patch
 
 BuildRequires:	bison
 BuildRequires:	llvm12