From dec26b7da2ee61641eac8909d0fc2a9f8985216d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
Date: Fri, 19 May 2023 19:02:08 +0200
Subject: [PATCH] backgroundApps: Allow activating apps

Now that we track apps instead of instances, we can make the menu
items activatable, because the corresponding action is no longer
app specific (like activating a particular tab): We can simply
activate the app, which hopefully will bring it to the foreground
again.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2790>
---
 js/ui/status/backgroundApps.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/js/ui/status/backgroundApps.js b/js/ui/status/backgroundApps.js
index 6fd22ea1e..f2bee8884 100644
--- a/js/ui/status/backgroundApps.js
+++ b/js/ui/status/backgroundApps.js
@@ -34,8 +34,6 @@ var BackgroundAppMenuItem = GObject.registerClass({
         delete params.message;
 
         super._init(app.get_name(), app.get_icon(), {
-            activate: false,
-            reactive: false,
             ...params,
         });
 
@@ -93,6 +91,8 @@ var BackgroundAppMenuItem = GObject.registerClass({
 
         closeButton.connect('clicked', () => this._quitApp().catch(logError));
 
+        this.connect('activate', () => this.app.activate());
+
         this.connect('destroy', () => this._onDestroy());
     }