From 62ad588aa982cd4305a8817cf21f0818234f4354 Mon Sep 17 00:00:00 2001
From: Lauri Ojansivu <x@xet7.org>
Date: Tue, 7 Oct 2025 00:35:17 +0300
Subject: [PATCH] Hide extra keyboard shortcuts toggle. Thanks to xet7.

---
 client/components/boards/boardBody.js |  2 ++
 client/components/main/layouts.jade   | 41 ++++++++++++++-------------
 2 files changed, 23 insertions(+), 20 deletions(-)

diff --git a/client/components/boards/boardBody.js b/client/components/boards/boardBody.js
index 2a9076895..c8026c6f2 100644
--- a/client/components/boards/boardBody.js
+++ b/client/components/boards/boardBody.js
@@ -107,6 +107,7 @@ BlazeComponent.extendComponent({
         el.removeAttribute('tabindex');
       }
     });
+    /*
     // Add a toggle button for keyboard shortcuts accessibility
     if (!document.getElementById('wekan-shortcuts-toggle')) {
       const toggleContainer = document.createElement('div');
@@ -136,6 +137,7 @@ BlazeComponent.extendComponent({
         window.toggleWekanShortcuts(e.target.checked);
       });
     }
+    */
     // Ensure toggle-buttons, color choices, reactions, renaming, and calendar controls are focusable and have ARIA roles
     document.querySelectorAll('.js-toggle').forEach(function(el) {
       el.setAttribute('tabindex', '0');
diff --git a/client/components/main/layouts.jade b/client/components/main/layouts.jade
index 4afd3925e..fe78f4f2f 100644
--- a/client/components/main/layouts.jade
+++ b/client/components/main/layouts.jade
@@ -1,23 +1,24 @@
-html(lang="{{TAPi18n.getLanguage()}}")
-  head
-  title
-  meta(name="viewport" content="width=device-width, initial-scale=1")
-  meta(http-equiv="X-UA-Compatible" content="IE=edge")
-  //- XXX We should use pathFor in the following `href` to support the case
-    where the application is deployed with a path prefix, but it seems to be
-    difficult to do that cleanly with Blaze -- at least without adding extra
-    packages.
-  link(rel="shortcut icon" type="image/x-icon" href="/favicon.ico")
-  link(rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png")
-  link(rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png")
-  link(rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png")
-  link(rel="manifest" crossOrigin="use-credentials" href="/site.webmanifest")
-  link(rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5")
-  meta(name="apple-mobile-web-app-title" content="Wekan")
-  meta(name="application-name" content="Wekan")
-  meta(name="msapplication-TileColor" content="#00aba9")
-  meta(name="theme-color" content="#ffffff")
-  //link(rel="stylesheet" type="text/css" class="__meteor-css__" href="css/html5-default-theme.css")
+template(name="main")
+  html(lang="{{TAPi18n.getLanguage}}")
+    head
+      title
+      meta(name="viewport" content="width=device-width, initial-scale=1")
+      meta(http-equiv="X-UA-Compatible" content="IE=edge")
+      //- XXX We should use pathFor in the following `href` to support the case
+        where the application is deployed with a path prefix, but it seems to be
+        difficult to do that cleanly with Blaze -- at least without adding extra
+        packages.
+      link(rel="shortcut icon" type="image/x-icon" href="/favicon.ico")
+      link(rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png")
+      link(rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png")
+      link(rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png")
+      link(rel="manifest" crossOrigin="use-credentials" href="/site.webmanifest")
+      link(rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5")
+      meta(name="apple-mobile-web-app-title" content="Wekan")
+      meta(name="application-name" content="Wekan")
+      meta(name="msapplication-TileColor" content="#00aba9")
+      meta(name="theme-color" content="#ffffff")
+      //link(rel="stylesheet" type="text/css" class="__meteor-css__" href="css/html5-default-theme.css")
 
 template(name="userFormsLayout")
   section.auth-layout